public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@upchuck.cygnus.com>
To: ehr@listworks.com
Cc: "'Robert Lipe'" <robertlipe@usa.net>, egcs@egcs.cygnus.com
Subject: Re: DG/UX Port - Giving Up!!
Date: Mon, 31 May 1999 21:36:00 -0000	[thread overview]
Message-ID: <2433.926380158@upchuck.cygnus.com> (raw)
Message-ID: <19990531213600.OAHIB4Ll5iayoAHW6CzD9Y2IUB-rmiEgksFWwo54RDQ@z> (raw)
In-Reply-To: <078601be9b1a$64c43db0$65c8c8c8@ehrpc.listworks.com>

  In message < 078601be9b1a$64c43db0$65c8c8c8@ehrpc.listworks.com >you write:
  > My assumption was since that gdb knew the source code file and line, that
  > it must be able to read something in the debugging info.  Is that in the
  > symbol table?
GDB can get symbols from either the minimal symbol table or from the debug
symbols.

On some platforms it may even be able to get symbols from the dynamic symbol
table, though I've never actually verified if this works.

jeff

  parent reply	other threads:[~1999-05-31 21:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-10  7:51 Eric Raskin
1999-05-10  8:49 ` Robert Lipe
1999-05-10  9:56   ` Eric Raskin
1999-05-10 10:24     ` Robert Lipe
1999-05-10 12:24       ` Eric Raskin
1999-05-10 13:00         ` Robert Lipe
1999-05-31 21:36           ` Robert Lipe
1999-05-10 16:52         ` Jeffrey A Law [this message]
1999-05-31 21:36           ` Jeffrey A Law
1999-05-31 21:36         ` Eric Raskin
1999-05-31 21:36       ` Robert Lipe
1999-05-10 17:02     ` Jeffrey A Law
1999-05-31 21:36       ` Jeffrey A Law
1999-05-31 21:36     ` Eric Raskin
1999-05-10 16:58   ` Jeffrey A Law
1999-05-31 21:36     ` Jeffrey A Law
1999-05-31 21:36   ` Robert Lipe
1999-05-31 21:36 ` Eric Raskin

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=2433.926380158@upchuck.cygnus.com \
    --to=law@upchuck.cygnus.com \
    --cc=egcs@egcs.cygnus.com \
    --cc=ehr@listworks.com \
    --cc=robertlipe@usa.net \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).