Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@imgtec.com>
To: <gdb-patches@sourceware.org>
Cc: Yao Qi <yao.qi@linaro.org>, Joel Brobecker <brobecker@adacore.com>
Subject: [PATCH] mem-break: Fix breakpoint insertion location
Date: Tue, 01 Aug 2017 16:36:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1708011707230.29991@tp.orcam.me.uk> (raw)

Fix a commit cd6c3b4ffc4e ("New gdbarch methods breakpoint_kind_from_pc 
and sw_breakpoint_from_kind") regression and restore the use of 
->placed_size rather than ->reqstd_address as the location for a memory 
breakpoint to be inserted at.  Previously `gdbarch_breakpoint_from_pc' 
was used that made that adjustment in `default_memory_insert_breakpoint' 
from the preinitialized value, however with the said commit that call is 
gone, so the passed ->placed_size has to be used for the initialization.

The regression manifests itself as the inability to debug any MIPS/Linux 
compressed ISA dynamic executable as GDB corrupts the dynamic loader 
with one of its implicit breakpoints, causing the program to crash, as 
seen for example with the `mips-linux-gnu' target, o32 ABI, MIPS16 code, 
and the gdb.base/advance.exp test case:

(gdb) continue
Continuing.

Program received signal SIGBUS, Bus error.
_dl_debug_initialize (ldbase=0, ns=0) at dl-debug.c:51
51	    r = &_r_debug;
(gdb) FAIL: gdb.base/advance.exp: Can't run to main

	gdb/
	* mem-break.c (default_memory_insert_breakpoint): Use 
	`->placed_address' rather than `->reqstd_address' for the 
	breakpoint location.
---
Hi,

 No regressions between plain commit cd6c3b4ffc4e^ and commit cd6c3b4ffc4e 
with this change applied in `mips-linux-gnu', o32, MIPS16 testing.  This 
brings that configuration back to sanity.

 OK for master and (as a grave regression) for 8.0?

  Maciej

---
 gdb/mem-break.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

gdb-mem-break-placed-address.diff
Index: binutils/gdb/mem-break.c
===================================================================
--- binutils.orig/gdb/mem-break.c	2017-07-30 22:45:34.000000000 +0100
+++ binutils/gdb/mem-break.c	2017-07-30 23:41:28.595612206 +0100
@@ -37,7 +37,7 @@ int
 default_memory_insert_breakpoint (struct gdbarch *gdbarch,
 				  struct bp_target_info *bp_tgt)
 {
-  CORE_ADDR addr = bp_tgt->reqstd_address;
+  CORE_ADDR addr = bp_tgt->placed_address;
   const unsigned char *bp;
   gdb_byte *readbuf;
   int bplen;


             reply	other threads:[~2017-08-01 16:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01 16:36 Maciej W. Rozycki [this message]
2017-08-02 17:53 ` Maciej W. Rozycki
2017-08-04 13:17 ` Simon Marchi
2017-08-04 13:58   ` Maciej W. Rozycki
2017-08-04 13:24 ` Yao Qi
2017-08-04 14:13   ` [PATCH v2] PR breakpoints/21886: " Maciej W. Rozycki
2017-08-07 15:35     ` Yao Qi
2017-08-07 16:05       ` Maciej W. Rozycki
2017-08-09  7:44         ` Yao Qi
2017-08-11 14:31           ` Maciej W. Rozycki
2017-08-11 15:12             ` Yao Qi
2017-08-11 16:14               ` Maciej W. Rozycki

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=alpine.DEB.2.00.1708011707230.29991@tp.orcam.me.uk \
    --to=macro@imgtec.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao.qi@linaro.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