From: Peter Barada <pbarada@mail.wm.sps.mot.com>
To: gdb@sources.redhat.com, libc-alpha@sources.redhat.com
Cc: Peter.Barada@motorola.com, peter@baradas.org
Subject: Re: Trouble with gdbserver from gdb-5.3, glibc-2.3.2 on ppc32
Date: Wed, 10 Sep 2003 18:58:00 -0000 [thread overview]
Message-ID: <200309101858.h8AIwVL08960@hyper.wm.sps.mot.com> (raw)
In-Reply-To: <200309101741.h8AHf6I06309@hyper.wm.sps.mot.com> (message from Peter Barada on Wed, 10 Sep 2003 13:41:06 -0400)
>Now that the power is back on(and our network is up and runnig again),
>I looked again and indeed its statically linked. I'll try dynamically
>linking it and see what happens.
Ok, my applications runs if its dynamically linked, but if I debug it
using gdb-5.3/gdbserver I get the following:
(gdb) set solib-absolute-prefix /dev/null
(gdb) set solib-search-path /usr/local/wave/x-ppc-linux2/powerpc-linux/lib
(gdb) tar remo 10.1.1.3:3001
Remote debugging using 10.1.1.3:3001
0x3000f430 in ?? ()
(gdb) i b
No breakpoints or watchpoints.
(gdb) b main
Breakpoint 4 at 0x10001eb0: file ../mn/mn.c, line 709.
(gdb) c
Continuing.
Error while reading shared library symbols:
DW_FORM_strp pointing outside of .debug_str section
Error while reading shared library symbols:
DW_FORM_strp pointing outside of .debug_str section
[New Thread 16384]
Error while reading shared library symbols:
DW_FORM_strp pointing outside of .debug_str section
Error while reading shared library symbols:
DW_FORM_strp pointing outside of .debug_str section
Error while reading shared library symbols:
DW_FORM_strp pointing outside of .debug_str section
Error while reading shared library symbols:
DW_FORM_strp pointing outside of .debug_str section
[Switching to Thread 16384]
Breakpoint 4, main (argc=3, argv=0x7ffffe04) at ../mn/mn.c:709
(gdb) i sh
From To Syms Read Shared Object Library
0x0ff732dc 0x0ffa3994 Yes /home/mylocal/local/wave/x-ppc-linux2/powerpc-linux/lib/libm.so.6
0x0fefc0f4 0x0ff05140 Yes /home/mylocal/local/wave/x-ppc-linux2/powerpc-linux/lib/libpthread.so.0
0x0fdbea20 0x0feb64e4 No /home/mylocal/local/wave/x-ppc-linux2/powerpc-linux/lib/libc.so.6
0x30001e00 0x300126f0 No /home/mylocal/local/wave/x-ppc-linux2/powerpc-linux/lib/ld.so.1
(gdb) i thr
* 1 Thread 16384 main (argc=3, argv=0x7ffffe04) at ../mn/mn.c:709
(gdb) s
(gdb) s
(gdb) c
Continuing.
[New Thread 32769]
Program received signal ?, Unknown signal.
[Switching to Thread 32769]
0x0fdd4d5c in ?? ()
from /home/mylocal/local/wave/x-ppc-linux2/powerpc-linux/lib/libc.so.6
(gdb) where
#0 0x0fdd4d5c in ?? ()
from /home/mylocal/local/wave/x-ppc-linux2/powerpc-linux/lib/libc.so.6
(gdb) i thr
* 2 Thread 32769 0x0fdd4d5c in ?? ()
from /home/mylocal/local/wave/x-ppc-linux2/powerpc-linux/lib/libc.so.6
1 Thread 16384 0x0fdd4d5c in ?? ()
from /home/mylocal/local/wave/x-ppc-linux2/powerpc-linux/lib/libc.so.6
(gdb) disp/3i $pc
1: x/3i $pc
0xfdd4d5c: mfcr r0
0xfdd4d60: mr r31,r3
0xfdd4d64: andis. r9,r0,4096
(gdb) si
And gdb never comes back to me(whether I us step, stepi, continue, and
it is interruptable with a C-c, but the pc is still at 0xfdd4d5c).
Any suggestions as to why its not executing under gdb are highly appreciated!
--
Peter Barada Peter.Barada@motorola.com
Wizard 781-852-2768 (direct)
WaveMark Solutions(A Motorola Company) 781-270-0193 (fax)
next prev parent reply other threads:[~2003-09-10 18:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 20:32 Peter Barada
2003-09-09 20:46 ` Roland McGrath
2003-09-09 21:15 ` Peter Barada
2003-09-09 21:24 ` Roland McGrath
2003-09-09 21:23 ` Daniel Jacobowitz
2003-09-09 21:30 ` Daniel Jacobowitz
2003-09-09 21:39 ` Roland McGrath
2003-09-09 21:40 ` Daniel Jacobowitz
2003-09-10 0:18 ` Peter Barada
2003-09-10 17:41 ` Peter Barada
2003-09-10 18:58 ` Peter Barada [this message]
2003-09-10 0:34 ` Peter Barada
2003-09-10 0:49 ` Dan Kegel
2003-09-10 0:53 ` Peter Barada
2003-09-09 21:45 ` Dan Kegel
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=200309101858.h8AIwVL08960@hyper.wm.sps.mot.com \
--to=pbarada@mail.wm.sps.mot.com \
--cc=Peter.Barada@motorola.com \
--cc=gdb@sources.redhat.com \
--cc=libc-alpha@sources.redhat.com \
--cc=peter@baradas.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