Shared library debugging problem under Solaris 8

Shared library debugging problem under Solaris 8

[Alex Paker]

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

RE: Shared library debugging problem under Solaris 8

[Stéphane Graziani]

I have exactly the same problem on the current 5.3 version, and when I try to step into a shared library, I get sometimes a bus error and sometimes a segmentation fault from gdb...

I tried the last snapshot, but it can even not load my application.

Can somebody help us about this problem?

Stéphane GRAZIANI

> -----Original Message-----
> From: Alex Paker [ <mailto:alex@sela.co.il>]
> Sent: Monday, May 05, 2003 6:47 PM
> To: 'gdb@sources.redhat.com'
> Subject: Shared library debugging problem under Solaris 8
> 
> 
> 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
> 

  _____  

RE: Shared library debugging problem under Solaris 8

[Lev Assinovsky]

Try the latest snapshot of gdb. 
I had about the same problems and 
solved them by gdb+dejagnu-20030228 snapshot.
Good luck!
----
Lev Assinovsky
Aelita Software Corporation
O&S Core Division, Programmer
ICQ# 165072909


> -----Original Message-----
> From: Alex Paker [mailto:alex@sela.co.il]
> Sent: Monday, May 05, 2003 6:47 PM
> To: 'gdb@sources.redhat.com'
> Subject: Shared library debugging problem under Solaris 8
> 
> 
> 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
>