This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

breakpoints/2008: gdb fails to re-parse breakpoint condition


>Number:         2008
>Category:       breakpoints
>Synopsis:       gdb fails to re-parse breakpoint condition
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Fri Sep 09 21:08:01 UTC 2005
>Closed-Date:
>Last-Modified:
>Originator:     Tom Tromey <tromey@redhat.com>
>Release:        GNU gdb 6.3.50.20050811-cvs
>Organization:
>Environment:
x86 Fedora Core 2
>Description:
I set a breakpoint on a function in libgcj.
Then I make this breakpoint conditional:

cond 3 !strcmp (((char*) (*(class _Jv_VTable**) value).clas.name.data), "java.lang.NullPointerException")

At the time I make the breakpoint and conditional,
the current frame is a C++ frame.

I "cont".  gdb goes along ok for a while and then
I get many messages like this:

Error in re-setting breakpoint 3:
syntax error: near `*) (*(_Jv_VTable**) value).clas.name.data), "java.lang.NullPointerException")'

I can work around this problem by clearing the condition,
doing "set lang c++", and then adding the condition again.
Then gdb will not complain after a "cont".

>How-To-Repeat:

>Fix:

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]