From: "Wenxiang Dai" <wxdai@utstar.com>
To: "Daniel Jacobowitz" <drow@mvista.com>
Cc: <gdb@sources.redhat.com>
Subject: RE: gdbserver with PowerPC 8260
Date: Tue, 01 Oct 2002 16:28:00 -0000 [thread overview]
Message-ID: <NGBBJBGIILBMOINAKFMNCEAGCBAA.wxdai@utstar.com> (raw)
In-Reply-To: <20021001232109.GA21272@nevyn.them.org>
Yes, it's in my nfs lib directory, first time I try to run the gdbserver, it
says need the libthread_db, so I copy it into the nfs lib directory, then
the gdbserver can run, do u mean this library is not OK. I am using the
timesys package for the target. Thanks
-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@mvista.com]
Sent: Tuesday, October 01, 2002 7:21 PM
To: Wenxiang Dai
Cc: gdb@sources.redhat.com
Subject: Re: gdbserver with PowerPC 8260
> Program received signal SIG32, Real-time event 32.
If you get that message, multithreaded debug is not working. Is
libthread_db available on your target?
On Tue, Oct 01, 2002 at 07:13:16PM -0400, Wenxiang Dai wrote:
> I downloaded the latest GDB code "gdb+dejagnu-weekly-20021001.tar.bz2"
from
> sources.rehat.com, and rebuild the gdbserver and gdb for powerpc target,
> then I used the gdbserver to debug a multi-threads programme in target, if
> the breakpoint was set in main routine, it's OK, but if the break point
was
> set within any other child thread, the break point can be hit, however,
the
> debug cusor is not shown and the gdb say it is going to libc.so, if I say
n,
> the target programme will crash.
>
> I try to set "solib-search-path" to the target share lib path, the problem
> remains same.
>
> I used nfs to map the root file system to target.
>
> Any thought? Any suggestion?
>
> Thanks
>
> here is the display of the gdb
>
> GNU DDD 3.3.1 (i386-redhat-linux-gnu), by Dorothea Lütkehaus and Andreas
> Zeller.
> Copyright © 1995-1999 Technische Universität Braunschweig, Germany.
> Copyright © 1999-2001 Universität Passau, Germany.
> (gdb) set solib-search-path /exports/rfs/lib
> (gdb) file /home/wxdai/work/ipdslam/icm/apps/build/nmgt/bin.mpc/nmgt
> (gdb) list clib_pass.c:1
> Line 1 of "../../../../icm/apps/nmgt/cli_b/clib_pass.c" is at address
> 0x1003ff94 <enable_prv_func> but contains no code.
>
>
/home/wxdai/work/ipdslam/icm/apps/nmgt/cli_b/clib_pass.c:1:0:beg:0x1003ff94
> (gdb) break ../../../../icm/apps/nmgt/cli_b/clib_pass.c:20
> Breakpoint 1 at 0x1003ffb4: file
> ../../../../icm/apps/nmgt/cli_b/clib_pass.c,
> line 20.
> (gdb) target remote 172.16.133.231:12345
> 0x30010660 in ?? ()
> (gdb) handle SIG32 nostop
> (gdb) c
>
> Program received signal SIG32, Real-time event 32.
>
> Program received signal SIG32, Real-time event 32.
>
> Program received signal SIG32, Real-time event 32.
>
> Program received signal SIG32, Real-time event 32.
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
> 0x0ff12e00 in ngettext () from /lib/libc.so.6
> (gdb) c
>
>
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-10-01 23:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 16:11 Wenxiang Dai
2002-10-01 16:21 ` Daniel Jacobowitz
2002-10-01 16:28 ` Wenxiang Dai [this message]
2002-10-01 16:56 ` Daniel Jacobowitz
2002-10-01 17:41 ` help: gdb with no ROM/Flash Kam Lee
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=NGBBJBGIILBMOINAKFMNCEAGCBAA.wxdai@utstar.com \
--to=wxdai@utstar.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.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