>Number: 2190
>Category: gdb
>Synopsis: varobj.c:1471: internal-error: my_value_equal: Assertion
>`!value_lazy (val1)' failed
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Mon Oct 23 02:18:02 UTC 2006
>Closed-Date:
>Last-Modified:
>Originator: clement.chu@xxxxxxxxxxxxxxxxxx
>Release: GDB 6.5
>Organization:
>Environment:
Linux redhat fedora core 5
>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) "
This problem only occurs if I create MIVar for argument variable (argc). If I
don't create argument variable and create other variable instead of it, there
is no problem on gdb.
>How-To-Repeat:
gdb -i mi a.out
-break-insert main
-exec-run
-var-create - * argc
-var-update *
-exec-next 1
-var-update *
-exec-next 1
-var-update * (error occur)
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-csrc; name="test.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="test.c"
I2luY2x1ZGUgPG1waS5oPgojaW5jbHVkZSA8c3RkaW8uaD4KCmludAptYWluKGludCBhcmdjLCBj
aGFyICphcmd2W10pCnsKICAgaW50IHJhbms7CiAgIE1QSV9Jbml0KCZhcmdjLCAmYXJndik7CiAg
IE1QSV9Db21tX3JhbmsoTVBJX0NPTU1fV09STEQsICZyYW5rKTsKICAgcHJpbnRmKCJoaSBmcm9t
ICVkXG4iLCByYW5rKTsKCiAgIGlmIChyYW5rID4gMCkgewogICAgICAgcmFuayArPSAxOwogICAg
ICAgcHJpbnRmKCJpbiBoZXJlXG4iKTsKICAgICAgIHJhbmsgKj0yOwogICB9IGVsc2UgewogICAg
ICAgcmFuayArPSAzOwogICAgICAgcHJpbnRmKCJub3QgaW4gaGVyZVxuIik7CiAgICAgICByYW5r
ICo9IDQ7CiAgIH0KCiAgIE1QSV9GaW5hbGl6ZSgpOwogICByZXR1cm4gMDsKfQoK
|
