This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
breakpoints/1599: Can't set thread qualified breakpoints on an address
- From: sanders at mvista dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 30 Mar 2004 19:29:22 -0000
- Subject: breakpoints/1599: Can't set thread qualified breakpoints on an address
- Reply-to: sanders at mvista dot com
>Number: 1599
>Category: breakpoints
>Synopsis: Can't set thread qualified breakpoints on an address
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Tue Mar 30 19:38:01 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: sanders@mvista.com
>Release: GNU gdb 2003-08-12-cvs
>Organization:
>Environment:
Red Hat 9.0
>Description:
I want to set a breakpoint at address 0x300. This works fine:
b *0x300
Now I want to only have it break if it is thread 1, so I do:
b *0x300 thread 1
gdb returns:
A parse error in expression, near `thread 1'.
I chatted with Daniel Jacobowitz about the problem and he believes the problem is that what is after the '*' is treated as an expression and the expression parser can't handle running off the end the way the symbol name parser can.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: