From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13343 invoked by alias); 6 Aug 2008 17:07:51 -0000 Received: (qmail 13335 invoked by uid 22791); 6 Aug 2008 17:07:51 -0000 X-Spam-Check-By: sourceware.org Received: from Unknown (HELO SUKNPT8102.cogent-dsn.com) (80.156.46.154) by sourceware.org (qpsmtpd/0.31) with SMTP; Wed, 06 Aug 2008 17:06:54 +0000 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: GDB on Solaris 10 Date: Wed, 06 Aug 2008 17:07:00 -0000 Message-ID: <67068ED71049F24386084A94AD75497105E98B63@suknpt8102.cogent-dsn.local> References: <67068ED71049F24386084A94AD75497105E64087@suknpt8102.cogent-dsn.local> <20080805190810.GA4323@adacore.com> From: "Gareth Williams" To: "Joel Brobecker" Cc: X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-08/txt/msg00106.txt.bz2 Thanks, Joel, on the strength of that I tried it again. I got GDB 6.8 working for 32-bits just by fixing the warning mentioned in problem report 2481. The issue described there, I now think is due to trying to debug a 64-bit application with a 32-bit GDB. (That is what I was doing and I saw the same errors). This is explained here: http://sourceware.org/ml/gdb/2001-01/msg00195.html Building GDB for 64-bit was the problem. By googling I found out to try > CC=3D"gcc -m64" ./configure Is that the recommended method? I can't find this in the GDB documentation. There are various sparc64 targets in the Makefiles, so I tried things like > ./configure --target=3Dsparc64-sun-solaris2.10 But this just seems to give it a different label. (Or do I need both?) Is there a list of valid targets anywhere? There must be something clever going on behind the scenes because the link lines for 32-bit and 64-bit (when using CC=3D"gcc -m64") are quite different. With 64-bit I got complaints about undefined symbols wattr_on and wattr_off in the curses library, which is not a problem for the default 32-bit compile. Some more googling led me to: > CC=3D"gcc -m64" ./configure --disable-tui > make And I have a 64-bit GDB that kind of works! So thanks again for the help. For future reference I would be interested to know if this is the right way to compile 64-bit on Solaris, and (unless I have missed it) perhaps it needs to be documented somewhere? cheers Gareth Williams -----Original Message----- From: Joel Brobecker [mailto:brobecker@adacore.com]=20 Sent: 05 August 2008 20:08 To: Gareth Williams Cc: gdb@sourceware.org Subject: Re: GDB on Solaris 10 > Does anyone have GDB working on Solaris 10? Yes - we build GDB 6.8 on Solaris 10 for both 32 and 64 bits. We don't do anything particular to get it working, though, so I'm not sure what the problem might be in your case. --=20 Joel > Does anyone have GDB working on Solaris 10? >=20 > I have installed GDB 6.6 from http://www.sunfreeware.com. This works for > > 'hello world' but not for the multi-threaded application I need to debug. > The problem is essentially that described in problem report 2481: > > http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-> trail&database=3Dgdb&pr=3D2481=20 > > We also have compiled GDB 6.8 from source - and this does not work even for 'hello world'. > > bash-3.00$ gdb ./hello > > GNU gdb 6.8 > ... > This GDB was configured as "sparc-sun-solaris2.10"... > (gdb) break main > Breakpoint 1 at 0x10c60: file hello.cc, line 6. > (gdb) r > Starting program: /home/williamsg/hello > procfs: init_inferior, get_traced_signals line 4891, /proc/18409: Error 0. > (gdb) where > procfs: fetch_registers, get_gregs line 3768, /proc/18409: Error 0. > procfs: fetch_registers, get_gregs line 3768, /proc/18409: Error 0. > (gdb) > > So: does anyone have any version of GDB working on Solaris 10, for threaded applications? > > If so a hint would be nice :-) If not, is anyone interested in getting it > working? I may be able to spend a few days on this. Some pointers in the right direction would really help. > > cheers > > Gareth Williams