From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: [commit] Fix a C++ segfault
Date: Fri, 21 Jul 2006 00:43:00 -0000 [thread overview]
Message-ID: <20060721004329.GC3711@adacore.com> (raw)
In-Reply-To: <20060721004035.GB802@nevyn.them.org>
> > > 2006-07-20 Daniel Jacobowitz <dan@codesourcery.com>
> > >
> > > * eval.c (evaluate_struct_tuple): Skip static fields.
> >
> > I don't know C++ too much - how often is this likely to occur?
> > Would this be a safe patch for the branch?
>
> Safe, but not particularly relevant. None of this code has been used
> in years, it's quite clear - in fact 80% of that function is devoted to
> Chill support.
OK, so I won't bother putting it in the branch.
Thanks!
--
Joel
prev parent reply other threads:[~2006-07-21 0:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 22:54 Daniel Jacobowitz
2006-07-21 0:28 ` Joel Brobecker
2006-07-21 0:40 ` Daniel Jacobowitz
2006-07-21 0:43 ` Joel Brobecker [this message]
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=20060721004329.GC3711@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@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