From: Pedro Alves <pedro@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: fix load command bug [was : Re: Make remote-sim target always have a thread]
Date: Wed, 09 Jul 2008 11:18:00 -0000 [thread overview]
Message-ID: <200807091217.55334.pedro@codesourcery.com> (raw)
In-Reply-To: <20080707191949.GF11544@caradoc.them.org>
A Monday 07 July 2008 20:19:49, Daniel Jacobowitz wrote:
> On Fri, Jul 04, 2008 at 03:59:41PM +0100, Pedro Alves wrote:
> > gdb/
> > 2008-07-04 Pedro Alves <pedro@codesourcery.com>
> >
> > * symfile.c (load_command): Reopen the exec file and reread
> > symbols before anything else.
>
> This part is OK.
>
> > gdb/testsuite/
> > 2008-07-04 Pedro Alves <pedro@codesourcery.com>
> >
> > * gdb.base/chng-syms.exp: Don't expect "No symbol ...".
>
> This is unfortunate, since we want to verify that the user was
> informed. But I can't think of another way :-( OK.
Yeah, same sentiment here :-(
I've checked it in.
--
Pedro Alves
next prev parent reply other threads:[~2008-07-09 11:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 15:23 Make monitor targets always have a thread Pedro Alves
2008-07-03 18:04 ` Make remote-sim target " Pedro Alves
2008-07-04 15:00 ` fix load command bug [was : Re: Make remote-sim target always have a thread] Pedro Alves
2008-07-07 19:20 ` Daniel Jacobowitz
2008-07-09 11:18 ` Pedro Alves [this message]
2008-07-07 19:15 ` Make remote-sim target always have a thread Daniel Jacobowitz
2008-07-09 10:53 ` [ob] don't skip most of the testsuite... [was: Re: Make remote-sim target always have a thread] Pedro Alves
2008-07-09 12:36 ` Daniel Jacobowitz
2008-07-09 11:11 ` Make remote-sim target always have a thread Pedro Alves
2008-07-09 12:39 ` Daniel Jacobowitz
2008-07-07 19:12 ` Make monitor targets " Daniel Jacobowitz
2008-07-07 19:16 ` Stan Shebs
2008-07-07 19:22 ` Daniel Jacobowitz
2008-07-07 19:51 ` Stan Shebs
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=200807091217.55334.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=drow@false.org \
--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