From: gds <gds@chartertn.net>
To: insight@sources.redhat.com
Subject: Re: Crashes when "balloons" enabled
Date: Wed, 02 Apr 2008 14:00:00 -0000 [thread overview]
Message-ID: <ft03fq$ej0$1@ger.gmane.org> (raw)
In-Reply-To: <20080402000132.GA6223@nortel.com>
Doug Graham wrote:
> Not sure whether this helps or not as it probably doesn't fix the root
> cause, but I ran into this same problem some time ago and "fixed" it
> with the following patch (from Insight 6.5):
Applied patch. Think it helped. Was able to do "so gdbinit" once after
inspecting variables in balloons but crashed the second time. Will try a
similar null check at the point where mine is crashing. Thanks.
-gene
next prev parent reply other threads:[~2008-04-02 14:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 17:55 gds
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 [this message]
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='ft03fq$ej0$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).