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]

gdb/2188: gdb 6.5 -- internal error with "-var-update *" command


>Number:         2188
>Category:       gdb
>Synopsis:       gdb 6.5 -- internal error with "-var-update *" command
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Fri Oct 20 03:18:01 UTC 2006
>Closed-Date:
>Last-Modified:
>Originator:     clement.chu@csse.monash.edu.au
>Release:        unknown-1.0
>Organization:
>Environment:

>Description:
I start gdb with using MI interface.  If the program contains some argument variables, gdb will be killed after a few steps and call "-var-update *" command.  There is an error message from gdb as below:

-var-update *
~"varobj.c:1471: internal-error: my_value_equal: Assertion `!value_lazy (val1)' failed.\n"
~"A problem internal to GDB has been detected,\n"
~"further debugging may prove unreliable.\n"
~"Quit this debugging session? (y or n) "
>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]