From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/dwarf] Anonymous nested function causes SEGV during psymbol read
Date: Thu, 18 Mar 2010 18:39:00 -0000 [thread overview]
Message-ID: <20100318183858.GC2844@adacore.com> (raw)
In-Reply-To: <m3634u7t28.fsf@fleche.redhat.com>
> Joel> Yet another version: Instead of generating the complaint while creating
> Joel> the psymbols, I decided to generate them during the symtab creation
> Joel> phase. A couple of reasons:
> [...]
> Joel> That's why I like this version better...
>
> FWIW, seems reasonable to me.
Thanks! Checked in (I just lOoove that git cvsexportcommit thing :).
The only thing is the length of the commit messages. They now contain
the full description of the issue this patch is fixing, very close to
the initial email I send when submitting a patch. Is that a problem
with anyone?
--
Joel
next prev parent reply other threads:[~2010-03-18 18:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 19:02 Joel Brobecker
2010-02-19 3:06 ` Tom Tromey
2010-02-19 15:19 ` Joel Brobecker
2010-03-16 21:19 ` Joel Brobecker
2010-03-17 16:23 ` Joel Brobecker
2010-03-17 17:32 ` Tom Tromey
2010-03-18 18:39 ` Joel Brobecker [this message]
2010-03-18 19:00 ` Tom Tromey
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=20100318183858.GC2844@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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