public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: ramsey.haddad@yahoo.com To: insight-gnats@sources.redhat.com Subject: insight/316: insight variable balloon Date: Mon, 04 Jun 2007 17:33:00 -0000 [thread overview] Message-ID: <20070604173219.16647.qmail@sourceware.org> (raw) >Number: 316 >Category: insight >Synopsis: insight variable balloon >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Jun 04 17:33:01 UTC 2007 >Closed-Date: >Last-Modified: >Originator: ramsey.haddad@yahoo.com >Release: insight-6.6 >Organization: >Environment: FC6 Linux 2.6.20-1.2952.fc6 i686 i386 GNU/Linux >Description: I'v posted the insight/315 bug concerning cygwin and the quit. I tried the same file (mydbg.c) on FC6 and found out that the variable balloons option is causing insight to crash. I have insight compiled and installed in /opt/dummy/usr/bin and I put that at the forefront of the PATH variable >How-To-Repeat: gcc -g -o mydbg mydbg.c export PATH=/opt/dummy/usr/bin:$PATH insight ./mydbg Ctrl-N (for the gdb console) b 13 r hello world *move the mouse on any variables (like argc or anything) and it would immediatly seg fault. The cause of this problem seems to be the Variable Balloons option. Preferences -> Sources ... Variable Balloons "Off" But other problems still exist and it's trying to blame gdb for them. like when you try to add argc to the watchlist. it will give this error GDB: varobj.c:1471: internal-error: my_value_equal: Assertion `!value_lazy (val1)' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? Yes No pressing No is useless, the same window just keeps popping up right back at you. >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/x-csrc; name="mydbg.c" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="mydbg.c" I2luY2x1ZGUgPHN0ZGlvLmg+CgppbnQgZnVuYyhpbnQgYXJnYywgY2hhciAqYXJndltdKQp7Cglp bnQgaTsKCWZvciAoaSA9IDA7IGkgPCBhcmdjOyBpKyspCgkJcHJpbnRmKCIlc1xuIixhcmd2W2ld KTsKCXJldHVybiBhcmdjOwoKfQoKaW50IG1haW4oaW50IGFyZ2MsIGNoYXIgKmFyZ3ZbXSkKewoJ aW50IGk7Cglmb3IgKGkgPSAwOyBpIDwgYXJnYzsgaSsrKQoJCXByaW50ZigiJXNcbiIsYXJndltp XSk7CgoJZnVuYyhhcmdjLCBhcmd2KTsKCXJldHVybiAwOwoKfQoK
next reply other threads:[~2007-06-04 17:33 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-06-04 17:33 ramsey.haddad [this message] 2007-07-13 17:42 kseitz
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20070604173219.16647.qmail@sourceware.org \ --to=ramsey.haddad@yahoo.com \ --cc=insight-gnats@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).