From: Joel Brobecker <brobecker@adacore.com>
To: Luis Machado <luisgpm@linux.vnet.ibm.com>,
gdb-patches@sources.redhat.com
Subject: Re: [patch] Backtrace prints wrong argument value
Date: Mon, 22 Oct 2007 04:11:00 -0000 [thread overview]
Message-ID: <20071022033114.GB764@adacore.com> (raw)
In-Reply-To: <20071022010550.GA12211@caradoc.them.org>
> > > > > 2007-09-17 Luis Machado <luisgpm@br.ibm.com>
> > > > >
> > > > > * rs6000-tdep.c (ppc_dwarf2_frame_init_reg): New function.
> > > > > (rs6000_gdbarch_init): Install ppc_dwarf2_frame_init_reg as
> > > > > default dwarf2_frame_set_init_reg function.
> > > >
> > > > OK.
> > > >
> > >
> > > Thanks. I've commited this now.
> >
> > Luis asked me whether he could commit to the branch. I looked at the
> > patch, and it seems pretty safe to me. Does anyone have reservations
> > about this going to the branch? Daniel?
>
> Sounds fine to me.
Thanks for the feedback. Luis, I think this is enough approval for
it to go to the branch.
> There are now a pile (three, I believe) of PRs about Solaris build
> failures. Is there someone familiar with Solaris who could take a
> look at them? I think we have one at work that I could borrow for
> this, but it'll take me a while.
Could you point me to them? I will be tied up for the next two weeks
(I'm actually traveling oct-28/nov-02), but I can have a look when
I return.
I propose that we re-use the gdb-6.7 release wiki page to document
the issues we need to fix before gdb-6.7.1. I can add these Solaris
one.
--
Joel
next prev parent reply other threads:[~2007-10-22 3:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 19:13 Luis Machado
2007-04-25 19:25 ` Daniel Jacobowitz
2007-04-25 22:28 ` Luis Machado
2007-04-30 13:31 ` Luis Machado
2007-05-16 5:34 ` Luis Machado
2007-05-16 14:43 ` Daniel Jacobowitz
2007-05-16 15:20 ` Luis Machado
2007-05-16 15:23 ` Daniel Jacobowitz
2007-09-13 14:47 ` Luis Machado
2007-09-16 19:45 ` Daniel Jacobowitz
2007-09-17 13:05 ` Luis Machado
2007-09-17 13:15 ` Daniel Jacobowitz
2007-09-17 13:30 ` Luis Machado
2007-09-17 13:37 ` Daniel Jacobowitz
2007-09-17 13:46 ` Luis Machado
2007-09-17 14:00 ` Luis Machado
2007-09-17 14:04 ` Daniel Jacobowitz
2007-09-17 16:02 ` Luis Machado
2007-09-17 17:15 ` Luis Machado
2007-09-17 17:18 ` Daniel Jacobowitz
2007-09-17 17:34 ` Luis Machado
2007-09-17 17:48 ` Daniel Jacobowitz
2007-10-03 14:58 ` Luis Machado
2007-10-21 21:41 ` Luis Machado
2007-10-22 0:03 ` Joel Brobecker
2007-10-22 1:20 ` Daniel Jacobowitz
2007-10-22 4:11 ` Joel Brobecker [this message]
2007-10-24 20:50 ` Daniel Jacobowitz
2007-10-24 20:59 ` Joel Brobecker
2007-10-24 21:01 ` Daniel Jacobowitz
2007-10-24 22:23 ` Pedro Alves
2007-10-24 22:38 ` Pedro Alves
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=20071022033114.GB764@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.com \
--cc=luisgpm@linux.vnet.ibm.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