From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14724 invoked by alias); 5 May 2003 14:20:40 -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 14717 invoked from network); 5 May 2003 14:20:39 -0000 Received: from unknown (HELO gate.algorithm.aelita.com) (212.176.18.2) by sources.redhat.com with SMTP; 5 May 2003 14:20:39 -0000 Received: from bagman.edm.com ([10.0.0.4]) by gate.algorithm.aelita.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with ESMTP id com for ; Mon, 5 May 2003 18:16:57 +0400 content-class: urn:content-classes:message Subject: RE: Shared library debugging problem under Solaris 8 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Mon, 05 May 2003 14:20:00 -0000 Message-ID: <3F6F4712B759A34ABD453A8B39C10D6260E22D@bagman.edm.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Lev Assinovsky" To: "Alex Paker" , X-SW-Source: 2003-05/txt/msg00051.txt.bz2 Try the latest snapshot of gdb.=20 I had about the same problems and=20 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 >=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