From: Daniel Jacobowitz <drow@false.org>
To: James E Wilson <wilson@specifix.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] fix dwarf2 missing frame base problem
Date: Sun, 13 Nov 2005 18:40:00 -0000 [thread overview]
Message-ID: <20051113182753.GC3599@nevyn.them.org> (raw)
In-Reply-To: <1131745786.12420.19.camel@aretha.corp.specifix.com>
On Fri, Nov 11, 2005 at 01:49:47PM -0800, James E Wilson wrote:
> On Thu, 2005-11-03 at 10:59, James E Wilson wrote:
> > This fixes GCC PR 24490, which I refiled as GDB PR 2024.
> > http://sources.redhat.com/ml/gdb-patches/2005-11/msg00059.html
>
> Could someone please review this patch? I never received permission to
> install it. Also, I noticed that a gdb-6.4 branch was created last
> week. May I also have permission to add it to the branch? It would be
> nice if gdb-6.4 worked correctly with gcc-4.1.
This is OK for both head and branch. Could you please use a temporary
variable though? You're out to 82 columns.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-13 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 20:03 James E Wilson
2005-11-12 2:38 ` James E Wilson
2005-11-13 18:40 ` Daniel Jacobowitz [this message]
2005-11-15 8:52 ` James E Wilson
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=20051113182753.GC3599@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=wilson@specifix.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