From: "xchen" <xchen@sunrisetelecom.com.cn>
To: <gdb@sourceware.org>
Subject: gdb search wrong source file
Date: Thu, 27 Sep 2007 10:41:00 -0000 [thread overview]
Message-ID: <20070927104100.0fwhMnEWgEvFj8YA8xggG7GACCX67QxNFrdo9v1Sx7E@z> (raw)
Hi,
I use gdbserver run on my board. The problem is that gdb search wrong
source file.Blowed is my snapshot.
Breakpoint 1, 0x1000a5cc in main ()
(gdb) list
1 in ../sysdeps/powerpc/powerpc32/elf/start.S
(gdb) info source
Current source file is ../sysdeps/powerpc/powerpc32/elf/start.S
Compilation directory is /var/tmp/BUILD/glibc-2.3.2/csu
Source language is asm.
Compiled with DWARF 2 debugging format.
Does not include preprocessor macro info.
(gdb) list
1 in ../sysdeps/powerpc/powerpc32/elf/start.S
(gdb) info sharedlibrary
From To Syms Read Shared Object Library
0x0ff940c0 0x0ff9cc84 Yes
/opt/montavista/pro/devkit/ppc/8xx/target/mnt/cf/shared/lib/libpthread.so.0
0x0ff5fc24 0x0ff63bb4 Yes
/opt/montavista/pro/devkit/ppc/8xx/target/mnt/cf/shared/lib/librt.so.1
0x0feb9a78 0x0ff198bc Yes
/opt/montavista/pro/devkit/ppc/8xx/target/mnt/cf/shared/lib/libstdc++.so.5
0x0fdae728 0x0fe1e998 Yes
/opt/montavista/pro/devkit/ppc/8xx/target/mnt/cf/shared/lib/libm.so.6
0x0fd7da40 0x0fd86f3c Yes
/opt/montavista/pro/devkit/ppc/8xx/target/lib/libgcc_s.so.1
0x0fc32ad0 0x0fd3a1fc Yes
/opt/montavista/pro/devkit/ppc/8xx/target/lib/libc.so.6
0x30001f90 0x30013760 Yes
/opt/montavista/pro/devkit/ppc/8xx/target/lib/ld.so.1
(gdb) pwd
Working directory /home/chenxi/cpu_io_v106_20070910/cpu_v106_af/cpu_v/Debug.
(gdb) show directories
Source directories searched: $cdir:$cwd
Library loaded correctly. I try to use dir to add all my path, but gdb think
current source file is start.s. Actually root.cpp should be the current
file. How can I make it right. BTW last month, gdbserver don't have this
bug when I use it debug.
Thx,
Xi
next reply other threads:[~2007-09-27 8:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 10:41 xchen [this message]
[not found] <20070927082957.51BBB9829E@nan.false.org>
2007-09-27 12:07 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
2007-09-27 10:41 xchen
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=20070927104100.0fwhMnEWgEvFj8YA8xggG7GACCX67QxNFrdo9v1Sx7E@z \
--to=xchen@sunrisetelecom.com.cn \
--cc=gdb@sourceware.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