Daniel Jacobowitz wrote:
> On Tue, May 27, 2008 at 01:39:18PM -0400, Arthur Meacham wrote:
>> I am having the same problem. It is making life very difficult. Is
>> there something I can do, aside from completely downgrade?
>
> Sorry, you've really got to ask the kernel maintainers; it's a kernel
On Tue, May 27, 2008 at 01:39:18PM -0400, Arthur Meacham wrote:
> I am having the same problem. It is making life very difficult. Is
> there something I can do, aside from completely downgrade?
Sorry, you've really got to ask the kernel maintainers; it's a kernel
bug, not a GDB bug.
--
Daniel
I am having the same problem. It is making life very difficult. Is
there something I can do, aside from completely downgrade?
(gdb: 6.8-debian
linux: 2.6.24-17-generic)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I see this behavior as well when debugging gcc.
ii gdb6.8-1
ii linux-image-2. 2.6.24-5
it doesn't happen with
ii linux-image-2. 2.6.22-6
so I suspect the i386/x86_64 arch merge might have broken this.
Richard.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "
Kernel maintainers, does this look familiar? Maybe one of the 2.6.24
patch releases broke this?
On Wed, Apr 09, 2008 at 01:32:16PM -0400, Jerry Quinn (ibm) wrote:
> Daniel Jacobowitz wrote:
>> On Wed, Apr 09, 2008 at 12:58:37PM -0400, Jerry Quinn wrote:
>>
>>> As an example, I've hit a break p
Daniel Jacobowitz wrote:
On Wed, Apr 09, 2008 at 12:58:37PM -0400, Jerry Quinn wrote:
As an example, I've hit a break point and printing values in a vector. The
first value prints fine, then gdb starts doing the following below. The
"set unwindonsignal on" doesn't help. I still get SIGTRAP
On Wed, Apr 09, 2008 at 12:58:37PM -0400, Jerry Quinn wrote:
> As an example, I've hit a break point and printing values in a vector. The
> first value prints fine, then gdb starts doing the following below. The
> "set unwindonsignal on" doesn't help. I still get SIGTRAPS after this,
> almost as
Package: gdb
Version: 6.7.1-2
Severity: normal
I'm having trouble with gdb stopping on SIGTRAP a lot. I can run up to the
first breakpoint, then sometimes I try to print or step and gdb will
claim that the program is responding to SIGTRAP. I'm debugging C++ code and
I'm doing nothing with signa
8 matches
Mail list logo
