public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: gds <gds@chartertn.net>
To: insight@sources.redhat.com
Subject: Crashes when "balloons" enabled
Date: Tue, 01 Apr 2008 17:55:00 -0000	[thread overview]
Message-ID: <fstste$hto$1@ger.gmane.org> (raw)

I have tried 6.5 to 6.8 and they all seem to crash after accessing a 
balloon for me. When I allow a balloon to pop-up the program crashes 
(disappears) typically after re-sourcing gdbinit in the terminal (i.e., 
so gdbinit), not immediately. Although I have rarely seen it crash when 
the mouse was over a cursor and a balloon was about to pop-up.

I saw this bug listed on a bug list on the insight site I think. No 
resolution was mentioned.

Is there a possible work-around for this? I have tried various 
preference setting and I have found nothing that prevents a crash 
(except disabling the very useful balloon feature).

I am building directly from source on fedora 8 and am currently using 
insight 6.6 since my rtos (rtems) includes gdb 6.6. Applying the rtems 
patches to gdb in insight has no effect on the crash. My target is arm.

I am doing remote debugging to a gdb server in a ethernet connected 
Macraigor mpDemon.

Thanks,
-gene

             reply	other threads:[~2008-04-01 17:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 17:55 gds [this message]
2008-04-01 18:00 ` Keith Seitz
2008-04-01 18:48   ` gds
2008-04-02  0:02     ` Doug Graham
2008-04-02 14:00       ` gds
2008-04-02 15:52       ` gds
2008-04-02 17:14         ` Doug Graham
2008-04-02 17:23         ` Keith Seitz
2008-04-02 17:44           ` Doug Graham
2008-04-02 18:01             ` Keith Seitz
2008-04-02 20:06               ` Doug Graham
2008-04-02 20:12                 ` Keith Seitz
2008-04-02 18:19           ` gds
2008-04-02 18:41             ` Keith Seitz
2008-06-29 17:56               ` Gene Smith
2008-04-01 22:12   ` gds
2008-04-01 22:32     ` gds
2008-04-02 17:16   ` gds

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='fstste$hto$1@ger.gmane.org' \
    --to=gds@chartertn.net \
    --cc=insight@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: link
Be 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).