Hi All,
I also have the same problem (Which is shown in the following message, which
is sent out one and half years ago) when I ran gdb-5.0(latest version download
from gnu ftp site)on SCO with my application.
I am wondering whether there is patch fix for gdb-5.0??
Thank you very much!
Ping
===================================================
Does anyone have comments on this?
Andrew
Robert Lipe wrote:
>
> I just spun the top of tree of the GDB5 branch on UnixWare 7. As a
> practical matter, the current thread support is somewhat more annoying
> than when GDB was thread-unaware.
>
> This GDB was configured as "i586-sco-sysv5uw7.1.1"...
> (gdb) run
> Starting program: /home/robertl/src/tmp/udiproto.timer/env/posix/./timertest
> [New LWP 1]
> [New Thread 1]
> [New Thread 2]
> [New Thread 3]
> [New Thread 4]
> [New LWP 2]
> [Exited Thread 2]
> [LWP 2 exited]
> [New LWP 3]
> procfs: fetch_registers, get_gregs line 3514, /proc/10235/lwp/2: No such file or directory.
> [Switching to LWP 2]
> procfs: fetch_registers, get_gregs line 3514, /proc/10235/lwp/2: No such file or directory.
> (gdb) c
> Continuing.
> procfs: fetch_registers, get_gregs line 3514, /proc/10235/lwp/2: No such file or directory.
>
> Note that at this point, it's trying to switch to an LWP that it knows
> has exited. The results are not good. But what happens next is even
> more annoying becuase now you're stuck in GDB and have to job control it
> and kill it.
>
> (gdb) q
> The program is running. Exit anyway? (y or n) y
> procfs: couldn't find pid 10235 in procinfo list.
> (gdb) q
> The program is running. Exit anyway? (y or n) y
> procfs: couldn't find pid 10235 in procinfo list.
>
> Nick, can you spot a ready fix for this?
>
> Thanx,
> RJL