From: <bogus@does.not.exist.com>
To: buildroot@busybox.net
Subject: No subject
Date: Wed, 23 Apr 2008 14:39:25 -0000 [thread overview]
Message-ID: <mailman.0.1209651073.1342.buildroot@uclibc.org> (raw)
0x40000930 0x40003f50 Yes
/home/osingla/buildroot-9260/buildroot/build_arm/staging_dir/lib/ld-uClibc.so.0
0x40011dd0 0x40018380 Yes
/home/osingla/buildroot-9260/buildroot/build_arm/staging_dir/lib/libpthread.so.0
0x40033800 0x40071e60 Yes
/home/osingla/buildroot-9260/buildroot/build_arm/staging_dir/lib/libc.so.0
(gdb) q
~$
When the thread has been created, it is not visible from the debugger.
It runs, but I can't put a breakpoint.
A few notes:
- I do not like the message "warning: Remote failure reply: E01", it
might mean that gdb host and gdbserver are not in sync for whatever
reason.
- If I put a breakpoint on the thread function, before 'cont', the
program terminates as soon the thread is created.
- the shared library 'thread_db' is not loaded (I think it should):
# cat /proc/2298/maps
00008000-00009000 r-xp 00000000 00:0c 4339 /tmp/test
00010000-00011000 rw-p 00000000 00:0c 4339 /tmp/test
00011000-00012000 rwxp 00011000 00:00 0 [heap]
40000000-40005000 r-xp 00000000 00:01 398 /lib/ld-uClibc-0.9.29.so
40005000-40006000 rw-p 40005000 00:00 0
4000c000-4000d000 r--p 00004000 00:01 398 /lib/ld-uClibc-0.9.29.so
4000d000-4000e000 rw-p 00005000 00:01 398 /lib/ld-uClibc-0.9.29.so
4000e000-40019000 r-xp 00000000 00:01 406 /lib/libpthread-0.9.29.so
40019000-40020000 ---p 40019000 00:00 0
40020000-40021000 r--p 0000a000 00:01 406 /lib/libpthread-0.9.29.so
40021000-40026000 rw-p 0000b000 00:01 406 /lib/libpthread-0.9.29.so
40026000-40028000 rw-p 40026000 00:00 0
40028000-400b5000 r-xp 00000000 00:01 414 /lib/libuClibc-0.9.29.so
400b5000-400bc000 ---p 400b5000 00:00 0
400bc000-400bd000 r--p 0008c000 00:01 414 /lib/libuClibc-0.9.29.so
400bd000-400be000 rw-p 0008d000 00:01 414 /lib/libuClibc-0.9.29.so
400be000-400c3000 rw-p 400be000 00:00 0
bebde000-bebf3000 rwxp befeb000 00:00 0 [stack]
I used linuxthreads (stable/old), and I checked 'pthreads debugging
support ' within uclibc menuconfig.
Any idea what I am missing?
TIA,
~Olivier
next reply other threads:[~2008-04-23 14:39 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 14:39 bogus [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-07 21:22 No subject bogus
2008-11-21 1:22 bogus
2008-10-23 17:17 bogus
2008-10-23 17:17 bogus
2008-10-23 17:17 bogus
2008-09-15 17:22 bogus
2008-09-15 17:22 bogus
2008-07-14 13:16 bogus
2008-07-14 13:16 bogus
2008-07-14 13:16 bogus
2008-07-14 13:16 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-03-17 22:01 bogus
2007-12-01 7:52 bogus
2007-12-01 7:52 bogus
2007-10-06 20:13 bogus
2007-10-06 20:13 bogus
2007-10-06 20:13 bogus
2007-07-23 18:04 bogus
2007-07-23 18:04 bogus
2007-06-23 20:07 bogus
2007-02-14 8:32 bogus
2007-02-14 8:32 bogus
2007-02-14 8:32 bogus
2007-02-14 8:32 bogus
2007-02-06 7:08 bogus
2007-02-06 7:08 bogus
2007-02-06 7:08 bogus
2007-02-06 7:08 bogus
2006-08-17 1:58 bogus
2006-08-17 1:58 bogus
2006-08-17 1:58 bogus
2006-08-17 1:58 bogus
2006-08-17 1:58 bogus
2006-08-17 1:58 bogus
2006-08-17 1:58 bogus
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=mailman.0.1209651073.1342.buildroot@uclibc.org \
--to=bogus@does.not.exist.com \
--cc=buildroot@busybox.net \
/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