From: Vladimir Prus <ghost@cs.msu.su>
To: gdb@sources.redhat.com
Subject: Re: (Another) Segfault in varobj.c
Date: Tue, 07 Aug 2007 15:08:00 -0000 [thread overview]
Message-ID: <f9a1ti$kv1$1@sea.gmane.org> (raw)
In-Reply-To: <B0D822BFECD50F4991F2516EA50F273C021ABDD7@NT-IRVA-0752.brcm.ad.broadcom.com>
Robert Norton wrote:
> Hi,
>
> 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?
It's hard to say without knowing if you have any local changes in varobj.c
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.
- Volodya
next prev parent reply other threads:[~2007-08-07 15:08 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 [this message]
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='f9a1ti$kv1$1@sea.gmane.org' \
--to=ghost@cs.msu.su \
--cc=gdb@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