This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
gdb/2425: When stopped at temporary breakpoint, thread-id = 0
- From: aristovski at qnx dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 5 Mar 2008 15:09:34 -0000
- Subject: gdb/2425: When stopped at temporary breakpoint, thread-id = 0
- Reply-to: aristovski at qnx dot com
>Number: 2425
>Category: gdb
>Synopsis: When stopped at temporary breakpoint, thread-id = 0
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Mar 05 15:18:02 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: aristovski@qnx.com
>Release: 6.7
>Organization:
>Environment:
>Description:
When stopped at main, thread-id is 0. The issue is visible in MI, but is not MI specific. This is the symptom:
*stopped,thread-id="0",frame={addr="0x08048925",func="main",args=[],file="main.cc",fullname="/space/src/testcases/PR55959/main.cc",line="9"}
Note "thread-id" is 0.
>How-To-Repeat:
-break-insert -t main
-exec-run
>Fix:
I can not provide a generic fix, but I can give a hint:
in normal_stop, we print thread-id but at that point thread list is empty, which causes "pid_to_thread_id" to return 0 (it didn't find the thread).
>Release-Note:
>Audit-Trail:
>Unformatted: