From: "Robert Norton" <rnorton@broadcom.com>
To: gdb@sourceware.org
Subject: FW: (Another) Segfault in varobj.c
Date: Tue, 07 Aug 2007 13:21:00 -0000 [thread overview]
Message-ID: <B0D822BFECD50F4991F2516EA50F273C021ABDF3@NT-IRVA-0752.brcm.ad.broadcom.com> (raw)
> -----Original Message-----
> From: Nick Roberts [mailto:nickrob@snap.net.nz]
> Sent: 07 August 2007 13:13
> To: Robert Norton
> Cc: gdb@sourceware.org
> Subject: Re: (Another) Segfault in varobj.c
> 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.
I didn't think 6.7 had been released yet?
> If you do need to be
> selective about the
> changes, I would just suggest including those from mi-cmd-var.c/h too.
Thanks.
> --
> Nick
> http://www.inet.net.nz/~nickrob
>
>
next reply other threads:[~2007-08-07 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 13:21 Robert Norton [this message]
2007-08-07 21:47 ` Nick Roberts
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=B0D822BFECD50F4991F2516EA50F273C021ABDF3@NT-IRVA-0752.brcm.ad.broadcom.com \
--to=rnorton@broadcom.com \
--cc=gdb@sourceware.org \
/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