From: "Paul N. Hilfinger" <hilfingr@otisco.mckusick.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: don't read coff line number unless we have symbols too
Date: Mon, 24 Jun 2002 19:30:00 -0000 [thread overview]
Message-ID: <200206250230.TAA21747@otisco.McKusick.COM> (raw)
OK. Further investigation (by Donn Terry) indicates that this change is
not a problem. In the cases on Interix that we were worried about, there
is still a linker symbol table with non-debugging symbols, and so the line
numbers aren't tossed after all.
Paul Hilfinger
next reply other threads:[~2002-06-25 2:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 19:30 Paul N. Hilfinger [this message]
2002-06-25 15:07 ` Jim Blandy
-- strict thread matches above, loose matches on Subject: below --
2002-06-24 12:32 Paul N. Hilfinger
2002-06-26 12:57 ` Jim Blandy
2002-03-06 15:58 Jim Blandy
2002-06-20 11:26 ` Jim Blandy
2002-06-20 11:39 ` Daniel Jacobowitz
2002-06-20 13:47 ` Jim Blandy
2002-06-24 5:57 ` Philippe De Muyter
2002-06-24 12:10 ` Joel Brobecker
2002-06-25 15:03 ` Jim Blandy
2002-06-26 1:03 ` Philippe De Muyter
2002-06-26 11:22 ` Jim Blandy
2002-08-21 22:52 ` Jim Blandy
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=200206250230.TAA21747@otisco.McKusick.COM \
--to=hilfingr@otisco.mckusick.com \
--cc=Hilfinger@otisco.mckusick.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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