Re: Bug#475206: gdb: SIGTRAP interfering with debugging
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 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 if gdb thinks there's a breakpoint on every statement from then on.
>> This is probably a kernel bug in the management of eflags. You might
>> want to check with the kernel maintainers.
>> I remember this coming up and being fixed, but it may have come back.
> I'm running
> linux-image-2.6.24-1-686 2.6.24-5
> which is the latest kernel available in unstable. I don't see any
> reference to eflags in the Debian changelog for the kernel package.