From: Alex Paker <alex@sela.co.il>
To: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Subject: Shared library debugging problem under Solaris 8
Date: Mon, 05 May 2003 13:42:00 -0000 [thread overview]
Message-ID: <C14A2A9E373CD61181660002B3325B230113908C@XANADU> (raw)
Hello,
I have a problem using gdb under Solaris 8 (sparc).
I use gcc 3.2.2 for building shared library. I use -g -fPIC compilation
options and gcc -shared -g for building the library. When I use gdb 5.0 it
can't understand gnu-v3 C++ mangling style, so gdb don't understand the
types (classes) and debugging is impossible. I tried to move to gdb 5.3 that
do understand this mangling style, but I stuck with another problem. When I
print stack after the program's crash all the stack frames that belongs to
my library are printed as following:
0x7f4d8250 in ?? () from /home/..../libfoo.so
It looks like I compile without any debugging information.
Another problem is when I try to set breakpoint in my shared library and
type 'continue' I get the following message:
(gdb) b 'Engine::get_data_from_registry(std::string&)'
Breakpoint 2 at 0x2b7f6c: file /home/..../Engine.cpp, line 1185.
(gdb) c
Continuing.
Warning:
Cannot insert breakpoint 2.
Error accessing memory address 0x2b7f6c: I/O error.
The same program may be running in another process.
One more thing. My shared library is very big (about 125M with debugging
information). Maybe it's a problem. When I build a little test (with shared
library and the same compilation options) I didn't get this problem. If the
problem is a library size, how can I handle it?
Any help will be very appreciated.
Thanks in advance,
Alex Paker
alex@sela.co.il
next reply other threads:[~2003-05-05 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 13:42 Alex Paker [this message]
2003-05-05 14:20 Lev Assinovsky
2003-08-21 15:37 Stéphane Graziani
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=C14A2A9E373CD61181660002B3325B230113908C@XANADU \
--to=alex@sela.co.il \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).