From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12621 invoked by alias); 23 Nov 2001 16:56:11 -0000 Mailing-List: contact gdb-help@sourceware.cygnus.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 12579 invoked from network); 23 Nov 2001 16:56:02 -0000 Received: from unknown (HELO gremlin.ics.uci.edu) (128.195.1.70) by sourceware.cygnus.com with SMTP; 23 Nov 2001 16:56:02 -0000 Received: from vino.ics.uci.edu ( vino.ics.uci.edu [128.195.11.198] ) by gremlin-relay.ics.uci.edu id aa19314 ; 23 Nov 2001 08:55 PST To: Eli Zaretskii Cc: gdb@sources.redhat.com Subject: GDB 5.1 on Solaris 2.8 From: Dan Nicolaescu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 11 Nov 2001 13:41:00 -0000 Message-ID: <200111230855.aa19314@gremlin-relay.ics.uci.edu> X-SW-Source: 2001-11/txt/msg00118.txt.bz2 > I've just built GDB 5.1 on Solaris 2.8, and I have a problem: GDB says > there's no debugging symbols in every executable I find, even though > they > were compiled and linkes with -g. dbx does find the debugging info. > >From what I see, GDB does find the minimal symbols, since I can put > breakpoints, but it cannot find the source line information. > > This is the first time I build GDB on Solaris, so I don't know whether > this is a known issue (not a word in README, though), or maybe I > goofed > during the build. > > The compiler used to compile GDB and the programs I try to debug was > SunWspro ANSI C compiler. > > Any ideas are welcome. It sounds that this is due to the fact that Sun's compiler+linker do not put the full debugging information in the binary by default. They only put some minimal debug info in the binary and leave the rest in the object files. Try compiling with -g -xs and see if you can debug then.