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: Clement Chu <clement dot chu at infotech dot monash dot edu dot au>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 24 Nov 2006 13:08:02 -0000
- Subject: Re: gdb/2188: gdb 6.5 -- internal error with "-var-update *" command
- Reply-to: Clement Chu <clement dot chu at infotech dot monash dot edu dot au>
The following reply was made to PR gdb/2188; it has been noted by GNATS.
From: Clement Chu <clement.chu@infotech.monash.edu.au>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/2188: gdb 6.5 -- internal error with "-var-update *" command
Date: Fri, 24 Nov 2006 23:58:21 +1100
Hi Daniel,
I forgot to mention that I am using openmpi version 1.0.2. Thanks.
Regards,
Clement
Daniel Jacobowitz wrote:
> (Next time, please respond to the bug tracking system, not to me
> personally. Thanks.)
>
> 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) "
>>
>
> I tried the testcase you sent me, using mpich. There was no error.
> Could you attach a compiled binary which shows the problem?
>
>