This is the mail archive of the
insight-prs@sourceware.org
mailing list for the Insight project.
insight/330: Debug Aborted
- From: asmprog32 at hotmail dot com
- To: insight-gnats at sources dot redhat dot com
- Date: 29 Apr 2008 16:41:28 -0000
- Subject: insight/330: Debug Aborted
- Reply-to: asmprog32 at hotmail dot com
>Number: 330
>Category: insight
>Synopsis: Debug Aborted
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Apr 29 16:43:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: asmprog32@hotmail.com
>Release: 6.7.1
>Organization:
>Environment:
>Description:
Every time a variable is suppressed by the compiler but defined into the context insight abort the debugging with
this message
varobj.c:1423:internal error: Assertion value_lazy(val1) failed ............ Quit this debug session ? Yes No
answering yes (ask if create a core file) and Abort
answering no the message continue to appear until you answer "yes" to Quit the debug session
>How-To-Repeat:
Compile this
#include <iostream>
int main(int argc, char * argv[])
{
return 0;
}
with g++ -o bug bug.cpp -g
or g++ -o bug bug.cpp -O0 -g
open insight run and try to display argc
the message varobj.c appear.
Because argc is not used g++ suppress it
from gdb console
print argc
Error: Cannot access memory at address 0x0
the problem disappear if i use argc or argv into main
because g++ don' t suppress them
>Fix:
None
>Release-Note:
>Audit-Trail:
>Unformatted: