It's possible it's another issue. The issue I saw was not dependent on gdb version however - tried a number of new/old versions and they all failed and it was entirely due to the kernel (strace of the gdb processes showed that 'ptrace' calls failed incorrectly). The 2.5 kernel might very well add additional requirements on the debugger...
/ David Hedbor
Previous text:
2003-02-12 23:21: Subject: Re: Weird problem with Image.SVG in Pike 7.4/7.5
On Wed, Feb 12, 2003 at 11:00:07PM +0100, David Hedbor @ Pike developers forum scribbled:
Gdb seems to be >broken on my development machine with the kernel 2.5 - it cannot set >breakpoints.
Seems to happen if you use the -ac patch set in 2.4 kernels as well. Quite annoying and the lack breakpoints is only part of the problem. Seems like ptrace() calls fails incorrectly. I don't know if this is a gdb bug but it rather seems like a kernel bug. Took me forever to figure out why my gdb didn't work.
It's a gdb bug, AFAIK. And in the 2.5 kernel there is new threading code which breaks gdb even more. It used to work before I last upgraded gdb - so it's not the kernel. Right now pressing 'r' makes gdb halt the process on SIGSTOP and then after 'c' report failure to set breakpoints.
marek
/ Brevbäraren
