From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22781 invoked by alias); 21 Aug 2003 15:37:53 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 22772 invoked from network); 21 Aug 2003 15:37:52 -0000 Received: from unknown (HELO isoft.fr) (194.51.220.95) by sources.redhat.com with SMTP; 21 Aug 2003 15:37:52 -0000 content-class: urn:content-classes:message Subject: RE: Shared library debugging problem under Solaris 8 Date: Thu, 21 Aug 2003 15:37:00 -0000 Message-ID: <692D23BBED62914F92EAD88B18217D8A021E02@winserver.isoft.fr> X-MS-Has-Attach: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MS-TNEF-Correlator: From: =?iso-8859-1?Q?St=E9phane_Graziani?= X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 To: "Liste Gdb (E-mail)" X-SW-Source: 2003-08/txt/msg00243.txt.bz2 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=E9phane GRAZIANI > -----Original Message----- > From: Alex Paker [ ] > Sent: Monday, May 05, 2003 6:47 PM > To: 'gdb@sources.redhat.com' > Subject: Shared library debugging problem under Solaris 8 >=20 >=20 > Hello, >=20=20 > I have a problem using gdb under Solaris 8 (sparc). > I use gcc 3.2.2 for building shared library. I use -g -fPIC=20 > compilation > options and gcc -shared -g for building the library. When I=20 > use gdb 5.0 it > can't understand gnu-v3 C++ mangling style, so gdb don't=20 > understand the > types (classes) and debugging is impossible. I tried to move=20 > to gdb 5.3 that > do understand this mangling style, but I stuck with another=20 > problem. When I > print stack after the program's crash all the stack frames=20 > that belongs to > my library are printed as following: > 0x7f4d8250 in ?? () from /home/..../libfoo.so > It looks like I compile without any debugging information. >=20=20 > Another problem is when I try to set breakpoint in my shared=20 > library and > type 'continue' I get the following message: > (gdb) b 'Engine::get_data_from_registry(std::string&)'=20 > 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. >=20 > One more thing. My shared library is very big (about 125M=20 > with debugging > information). Maybe it's a problem. When I build a little=20 > test (with shared > library and the same compilation options) I didn't get this=20 > problem. If the > problem is a library size, how can I handle it? >=20=20 > Any help will be very appreciated. >=20=20 > Thanks in advance, > Alex Paker > alex@sela.co.il >=20 _____=20=20