From: yuming5@attbi.com
To: gdb@sources.redhat.com
Subject: Help: cannot break into shared libraries on LinuxPPC
Date: Wed, 29 Jan 2003 00:15:00 -0000 [thread overview]
Message-ID: <20030129001500.tkVLodmnkghTStYIcZVjsR-OQvU1Dk32v3PVWga4Pi8@z> (raw)
Hello,
I have a problem that the gdb cannot break into the shared library -- actually,
it successfully breaks into the very first function defined in the shared
library source file(i.e. libPrint() in printlib.c, see the following example),
but failed to break into the other functions in that same source file (i.e.
libErrPrint() in printlib.c).
This was run with Linux2.2.17 on PowerPC. Other information:
gcc version 2.95.3, GNU ld and ar version 2.10.91.
Please see below the gdb output and the shell script used to create the
executable and shared library.
Any idea what went wrong?
Thanks,
Yuming
The gdb output:
it didn't break into libErrPrint().
------------------------------------------------------------------
... ...
Breakpoint 1, libPrint (a=3) at printlib.c:9
9 b = a;
(gdb) n
10 printf(">>>libPrint, %d\n",b);
(gdb)
>>>libPrint, 3
11 }
(gdb)
main () at main.c:13
13 libErrPrint(3);
(gdb) step
0x30025fc4 in .LC0 () from /lib/ld.so.1
(gdb) n
Single stepping until exit from function .LC0,
which has no line number information.
Breakpoint 2, 0x0ffdf4ac in libErrPrint (a=268367100)
from /home/mark/test/sharedlib/libmp_shr.so
(gdb)
Single stepping until exit from function libErrPrint,
which has no line number information.
>>>libErrPrint, 3
main () at main.c:14
14 return(0);
/* now returned back to main */
----------------------------------------------------------------
The example shell script used to create the shared library and executable (ttt):
----------------------------------------------------------------------
LIBPRE3=/home/mark/test/sharedlib
gcc -g -fPIC -c -o printlib.o printlib.c
ar r libfp_shr.a printlib.o
#create the shared library libmp_shr.so
ld -shared -soname libmp_shr.so -o libmp_shr.so -L$LIBPRE3 --whole-archive -
lfp_shr
ldconfig -l ../sharedlib/libmp_shr.so
#create executable ttt
gcc -g -I../sharedlib -L../sharedlib -o ttt main.c -lmp_shr
----------------------------------------------------------------
next reply other threads:[~2003-01-29 0:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 0:15 yuming5 [this message]
[not found] <200301290009.h0T09w123901@mx2.redhat.com>
2003-01-29 1:58 ` Kevin Buettner
-- strict thread matches above, loose matches on Subject: below --
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
2003-01-29 0:15 yuming5
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=20030129001500.tkVLodmnkghTStYIcZVjsR-OQvU1Dk32v3PVWga4Pi8@z \
--to=yuming5@attbi.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