From: "Robert Norton" <rnorton@broadcom.com>
To: "Vladimir Prus" <ghost@cs.msu.su>, gdb@sources.redhat.com
Subject: RE: (Another) Segfault in varobj.c
Date: Tue, 07 Aug 2007 16:12:00 -0000 [thread overview]
Message-ID: <B0D822BFECD50F4991F2516EA50F273C021ABE3D@NT-IRVA-0752.brcm.ad.broadcom.com> (raw)
In-Reply-To: <f9a1ti$kv1$1@sea.gmane.org>
> -----Original Message-----
> From: gdb-owner@sourceware.org
> [mailto:gdb-owner@sourceware.org] On Behalf Of Vladimir Prus
> Sent: 07 August 2007 16:09
> To: gdb@sources.redhat.com
> Subject: Re: (Another) Segfault in varobj.c
>
> It's hard to say without knowing if you have any local
> changes in varobj.c
Only an attempt to fix another bug which apparently is fixed in CVS
anyway.
> If not, then just grabbing varobj.c and maybe mi/* should be safe --
> at least as far as my patches are concerned, they are local
> to varobj.c.
OK. This is mostly what I wanted to know. I'll give it a try!
Robert
next prev parent reply other threads:[~2007-08-07 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 11:49 Robert Norton
2007-08-07 12:13 ` Nick Roberts
2007-08-07 15:08 ` Vladimir Prus
2007-08-07 16:12 ` Robert Norton [this message]
2007-08-08 18:01 ` Robert Norton
2007-08-08 18:09 ` Daniel Jacobowitz
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=B0D822BFECD50F4991F2516EA50F273C021ABE3D@NT-IRVA-0752.brcm.ad.broadcom.com \
--to=rnorton@broadcom.com \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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