gdb/2078: GNU/Linux, x86, catchpoint hit fork returns wrong pid on heavy load

markus@bluegap.ch markus@bluegap.ch
Tue Feb 7 11:58:00 GMT 2006


>Number:         2078
>Category:       gdb
>Synopsis:       GNU/Linux, x86, catchpoint hit fork returns wrong pid on heavy load
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Feb 07 11:58:01 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     markus@bluegap.ch
>Release:        GNU gdb 6.4.50.20060128-cvs
>Organization:
>Environment:
Ubuntu (Drapper) GNU/Linux x86,

Linux 2.6.15-14-k7
gcc version 4.0.3 20060115 (prerelease)
ldd (GNU libc) 2.3.6

This GDB was configured as "".
>Description:
I was trying to build an automatic debugging tool using the MI interpreter and a target which forks. A 'catch fork' should report the forks to which another gdb instance should attach, then. Unfortunately gdb seems to report pids that are slightly off. Mostly by just 1-5 counts.

I suspect that to happen only when other processes fork as well at the same time.
>How-To-Repeat:
If this was not a generally known mis-behaviour I would gladly put together some test code.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the Gdb-prs mailing list