This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: gdb/2188: gdb 6.5 -- internal error with "-var-update *" command
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 20 Oct 2006 03:58:01 -0000
- Subject: Re: gdb/2188: gdb 6.5 -- internal error with "-var-update *" command
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR gdb/2188; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: clement.chu@csse.monash.edu.au
Cc: gdb-gnats@sources.redhat.com, g.watson@computer.org
Subject: Re: gdb/2188: gdb 6.5 -- internal error with "-var-update *" command
Date: Thu, 19 Oct 2006 23:49:55 -0400
On Fri, Oct 20, 2006 at 03:13:18AM -0000, clement.chu@csse.monash.edu.au wrote:
> 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 is not enough information for us to reproduce your problem. Does
it always reproduce with a certain program? A certain series of
commands? What is your environment?
--
Daniel Jacobowitz
CodeSourcery