From: Daniel Jacobowitz <drow@false.org>
To: Paul Gilliam <pgilliam@us.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fixes testsuit/gdb.base/annota1.exp to deal with 'Breakpoint address adjusted'
Date: Wed, 27 Apr 2005 15:43:00 -0000 [thread overview]
Message-ID: <20050427154312.GC7765@nevyn.them.org> (raw)
In-Reply-To: <200504151638.04458.pgilliam@us.ibm.com>
On Fri, Apr 15, 2005 at 03:38:04PM -0800, Paul Gilliam wrote:
> OK. Â this is in partial responce to:
> Â Â Â Â Â Â Â Â http://sourceware.org/ml/gdb-patches/2005-04/msg00145.html
>
> There were two problems with gdb.base/annota1.exp. This patch is only for the first one.
>
> The problem here is that, in some architectures, a breakpoints in a shared object will be
> adjusted once the shared object is loaded. This cause two messages not accounted
> for by gdb.base/annota1.exp:
> Breakpoint address adjusted from ....
> Breakpoint <n> address previously adjusted from ...
>
> -=# Paul #=-
>
> --
> 2005-04-15 Paul Gilliam <pgilliam@us.ibm.com>
>
> * gdb.base/annota1.exp : Deal with messages caused by breakpoints in
> shared objects being adjusted.
This is OK. Please update the copyright year in annota1.exp.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-04-27 15:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 17:27 [PATCH] Fixes testsuit/gdb.base/annota1.exp Paul Gilliam
2005-04-14 19:36 ` Daniel Jacobowitz
2005-04-15 23:03 ` [PATCH] add new .exp file and a 'c' testfile to test backtrace limits etc Paul Gilliam
2005-04-30 18:49 ` Daniel Jacobowitz
2005-05-28 23:42 ` Daniel Jacobowitz
2005-04-15 23:38 ` [PATCH] Fixes testsuit/gdb.base/annota1.exp to deal with 'Breakpoint address adjusted' Paul Gilliam
2005-04-27 15:43 ` Daniel Jacobowitz [this message]
2005-04-27 21:47 ` [COMMIT] " Paul Gilliam
2005-04-15 23:38 ` [PATCH] Fixes testsuit/gdb.base/annota1.exp Paul Gilliam
2005-04-27 15:49 ` Daniel Jacobowitz
2005-04-27 20:02 ` Paul Gilliam
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=20050427154312.GC7765@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=pgilliam@us.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