Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Dan Nicolaescu <dann@godzilla.ICS.UCI.EDU>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb@sources.redhat.com
Subject: GDB 5.1 on Solaris 2.8
Date: Sun, 11 Nov 2001 13:41:00 -0000	[thread overview]
Message-ID: <200111230855.aa19314@gremlin-relay.ics.uci.edu> (raw)

  > 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. 


             reply	other threads:[~2001-11-23 16:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-11 13:41 Dan Nicolaescu [this message]
2001-11-11 18:14 ` gdb
  -- strict thread matches above, loose matches on Subject: below --
2001-11-26  4:16 debashis  mahata
2001-11-14  0:50 ` debashis  mahata
     [not found] <ur9r8qpa0l0.fsf@totally-fudged-out-message-id>
2001-11-11 21:24 ` Dan Nicolaescu
2001-11-12  1:49   ` Eli Zaretskii
2001-11-11 11:39 Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200111230855.aa19314@gremlin-relay.ics.uci.edu \
    --to=dann@godzilla.ics.uci.edu \
    --cc=eliz@is.elta.co.il \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox