This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
mi/2424: When stopped at temporary breakpoint, mi-message not correct
- From: aristovski at qnx dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 5 Mar 2008 15:03:31 -0000
- Subject: mi/2424: When stopped at temporary breakpoint, mi-message not correct
- Reply-to: aristovski at qnx dot com
>Number: 2424
>Category: mi
>Synopsis: When stopped at temporary breakpoint, mi-message not correct
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Mar 05 15:08:05 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: aristovski@qnx.com
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
When inferior stops at temporary breakpoint, message is:
*stopped,thread-id="0",frame={addr="0x08048925",func="main",args=[],file="main.cc",fullname="/space/src/testcases/PR55959/main.cc",line="9"}
without mentioning "reason=breakpoint-hit"
This causes issues for multithreaded programs.
>How-To-Repeat:
-break-insert -t main
-exec-run
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: