From: gomrioje <gomez.j@ikusi.es>
To: Daniel Jacobowitz <drow@false.org>
Cc: "Jesús Gómez Río" <gomez.j@ikusi.com>, gdb@sourceware.org
Subject: Re: Debugging pthread in ARM.
Date: Wed, 16 May 2007 17:46:00 -0000 [thread overview]
Message-ID: <1179337620.6692.49.camel@DAFPC5206.ikusi.net> (raw)
In-Reply-To: <20070516173752.GA14525@caradoc.them.org>
I have tried, and I get the same result.
Could it be link to:
http://sources.redhat.com/ml/gdb/2003-06/msg00535.html ?
It was about single-step in gdbserver for pthread_create?
2003-06-28 Daniel Jacobowitz <drow@mvista.com>
* linux-arm-low.c (arm_reinsert_addr): New function.
(the_low_target): Add arm_reinsert_addr.
Index: linux-arm-low.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbserver/linux-arm-low.c,v
retrieving revision 1.5
diff -u -p -r1.5 linux-arm-low.c
--- linux-arm-low.c 18 Nov 2002 00:37:50 -0000 1.5
+++ linux-arm-low.c 28 Jun 2003 23:53:49 -0000
@@ -80,6 +80,17 @@ arm_breakpoint_at (CORE_ADDR where)
return 0;
}
+/* We only place breakpoints in empty marker functions, and thread locking
+ is outside of the function. So rather than importing software single-step,
+ we can just run until exit. */
+static CORE_ADDR
+arm_reinsert_addr ()
+{
+ unsigned long pc;
+ collect_register_by_name ("lr", &pc);
+ return pc;
+}
+
struct linux_target_ops the_low_target = {
arm_num_regs,
arm_regmap,
@@ -89,7 +100,7 @@ struct linux_target_ops the_low_target =
arm_set_pc,
(const char *) &arm_breakpoint,
arm_breakpoint_len,
- NULL,
+ arm_reinsert_addr,
0,
arm_breakpoint_at,
};
Regards,
> On Wed, May 16, 2007 at 07:33:53PM +0200, gomrioje wrote:
> > set solib-absolute-prefix /app/arm/bitbaketmp/staging/arm-linux/lib/
>
> I'm not sure how many times I can try to explain this... this is the
> wrong path. You should be able to append "/lib/ld-linux.so.2" to that
> path and find your dynamic loader. Try removing "/lib/" from the end
> of your setting.
>
-
next prev parent reply other threads:[~2007-05-16 17:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 12:49 gomrioje
2007-05-15 12:58 ` Daniel Jacobowitz
2007-05-15 17:14 ` gomrioje
2007-05-15 17:21 ` Daniel Jacobowitz
2007-05-16 15:27 ` gomrioje
2007-05-16 15:35 ` Daniel Jacobowitz
2007-05-16 17:33 ` gomrioje
2007-05-16 17:38 ` Daniel Jacobowitz
2007-05-16 17:46 ` gomrioje [this message]
2007-05-16 17:52 ` Daniel Jacobowitz
2007-05-16 18:05 ` gomrioje
2007-05-16 18:11 ` Daniel Jacobowitz
2007-05-17 8:11 ` gomrioje
2007-05-17 9:28 ` Baurzhan Ismagulov
2007-05-17 12:34 ` gomrioje
2007-05-17 12:42 ` Daniel Jacobowitz
2007-05-15 18:42 ` Williams, Allen
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=1179337620.6692.49.camel@DAFPC5206.ikusi.net \
--to=gomez.j@ikusi.es \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=gomez.j@ikusi.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