From: Nick Roberts <nickrob@snap.net.nz>
To: "Robert Norton" <rnorton@broadcom.com>
Cc: gdb@sourceware.org
Subject: Re: (Another) Segfault in varobj.c
Date: Tue, 07 Aug 2007 12:13:00 -0000 [thread overview]
Message-ID: <18104.25042.969785.701585@kahikatea.snap.net.nz> (raw)
In-Reply-To: <B0D822BFECD50F4991F2516EA50F273C021ABDD7@NT-IRVA-0752.brcm.ad.broadcom.com>
> I have encountered another crash seemingly originating in varobj.c.
> Whilst I've been able to work around the segfault I think there are some
> deeper rooted problems and I remembered from our previous conversation
> that the whole of this has been rewritten for 6.7. How self contained
> were these changes, i.e. would it be hard to back port them for our 6.6
> based release? How risky would this be?
I can't say how risky it would be, I don't even understand why you would rather
backport to 6.6 than update to 6.7. If you do need to be selective about the
changes, I would just suggest including those from mi-cmd-var.c/h too.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2007-08-07 12:13 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 [this message]
2007-08-07 15:08 ` Vladimir Prus
2007-08-07 16:12 ` Robert Norton
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=18104.25042.969785.701585@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb@sourceware.org \
--cc=rnorton@broadcom.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