From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org, Pedro Alves <pedro@codesourcery.com>,
Pierre Muller <muller@ics.u-strasbg.fr>
Subject: New breakpoint_re_set call vs remote targets
Date: Wed, 24 Jun 2009 19:04:00 -0000 [thread overview]
Message-ID: <20090624190346.GA17908@caradoc.them.org> (raw)
This patch:
2009-06-17 Pierre Muller <muller@ics.u-strasbg.fr>
Pedro Alves <pedro@codesourcery.com>
* infcmd.c (post_create_inferior): Call breakpoint_re_set
after target
is pushed for watchpoint promotion to hardware watchpoint.
causes a testcase failure in nodebug.exp for arm-none-eabi. It will
affect all bare-metal targets.
The sequence is "target remote", which calls post_create_inferior
before any program exists on the remote side. Then later "load" fills
in the code. So we're doing prologue skipping - by reading target
memory - before we've written the code to target memory.
I have long had a plan to speed up prologue skipping by making it read
directly from the executable if possible. We're using the
executable's symbol table, so there's no reason to think the prologue
will have moved around on the target. The problems with this approach
are (A) it involves changing a lot of symbol readers, and (B) I'm not
sure if we want to handle fix-and-continue style function patching in
which case we need to read from the target anyway.
Thoughts? Any other approaches to fix this failure?
--
Daniel Jacobowitz
CodeSourcery
next reply other threads:[~2009-06-24 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 19:04 Daniel Jacobowitz [this message]
2009-06-24 23:36 ` Pedro Alves
2009-06-24 23:46 ` Daniel Jacobowitz
2009-06-24 23:53 ` Pedro Alves
2009-06-25 16:52 ` Doug Evans
2009-06-25 18:33 ` Daniel Jacobowitz
2009-06-25 19:36 ` Doug Evans
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=20090624190346.GA17908@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
--cc=pedro@codesourcery.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