SIGTRAP

SIGTRAP

[Burlen Loring]

Hi,

gdb seems to be having issues when I try to look inside stl vectors. I 
see this message


Program received signal SIGTRAP, Trace/breakpoint trap.

Then I end up inside operator[] code. Then the debugger becomes useless 
every next results in a SIGTRAP. I think this is new, but it could be 
that I am using vectors more lately but either way it's annoying. is 
this a known issue? is there a work around?

tycho:~$gdb -v
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".

thanks


-- 
Burlen Loring
Kitware, Inc.
R&D Engineer
28 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-371-3971 x137

Re: SIGTRAP

[Daniel Jacobowitz]

On Tue, Jul 29, 2008 at 03:05:50PM -0400, Burlen Loring wrote:
> Hi,
>
> gdb seems to be having issues when I try to look inside stl vectors. I  
> see this message
>
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
>
> Then I end up inside operator[] code. Then the debugger becomes useless  
> every next results in a SIGTRAP. I think this is new, but it could be  
> that I am using vectors more lately but either way it's annoying. is this 
> a known issue? is there a work around?

This was a bug in the IA-32 kernel for several releases.  See if an
upgrade is available?  I can't find the exact versions that were
affected.
>

-- 
Daniel Jacobowitz
CodeSourcery

Re: SIGTRAP

[Burlen Loring]

Daniel Jacobowitz wrote:
> On Tue, Jul 29, 2008 at 03:05:50PM -0400, Burlen Loring wrote:
>   
>> Hi,
>>
>> gdb seems to be having issues when I try to look inside stl vectors. I  
>> see this message
>>
>>
>> Program received signal SIGTRAP, Trace/breakpoint trap.
>>
>> Then I end up inside operator[] code. Then the debugger becomes useless  
>> every next results in a SIGTRAP. I think this is new, but it could be  
>> that I am using vectors more lately but either way it's annoying. is this 
>> a known issue? is there a work around?
>>     
>
> This was a bug in the IA-32 kernel for several releases.  See if an
> upgrade is available?  I can't find the exact versions that were
> affected.
>   

tycho:~$uname -a
Linux tycho 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 
GNU/Linux

There are probably newer kernels out there, hopefully they don't suffer 
from the same issue.

Thanks


-- 
Burlen Loring
Kitware, Inc.
R&D Engineer
28 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-371-3971 x137