From: Jim Blandy <jimb@redhat.com>
To: Alexander Larsson <alexl@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: Final separate debug info patch
Date: Tue, 19 Nov 2002 05:00:00 -0000 [thread overview]
Message-ID: <vt2fztxbuhg.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <vt2wunajgl9.fsf@zenia.red-bean.com>
Some other stuff I've noticed:
- In reread_symbols, it looks like we do throw away
objfile->separate_debug_objfile if it doesn't match any more, but I
don't see where we read in the new one. (I think this is the cause
of the reread.exp failure.)
- Similarly, if we start with an unseparated objfile, but then it is
changed to a separated objfile, I don't see where reread_symbols
loads the separated objfile's debug objfile.
- In reread_symbols, if the new objfile's debug link has a different
name, but the CRC's happen to match, it won't toss the old file. It
seems to me that we should re-run find_separate_debug_file from
scratch, and make sure the filename we get matches the existing
separate_debug_objfile's name.
In general, I'm not convinced that the change to reread_symbols really
covers all the cases. I'll try to fix it.
next prev parent reply other threads:[~2002-11-19 13:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 1:54 Alexander Larsson
2002-11-18 21:20 ` Jim Blandy
2002-11-18 21:32 ` Daniel Jacobowitz
2002-11-19 3:53 ` Jim Blandy
2002-11-18 23:47 ` Alexander Larsson
2002-11-19 3:38 ` Jim Blandy
2002-11-19 3:57 ` Alexander Larsson
2002-11-19 12:47 ` Alexander Larsson
2002-11-20 21:43 ` Jim Blandy
2002-11-20 23:35 ` Alexander Larsson
2002-11-19 5:00 ` Jim Blandy [this message]
2002-11-18 22:11 ` Jim Blandy
2002-11-18 23:51 ` Alexander Larsson
2002-11-19 0:02 ` Ulrich Drepper
2002-11-19 3:47 ` Jim Blandy
2002-11-19 3:53 ` Alexander Larsson
2002-11-19 4:38 ` Jim Blandy
2002-11-24 20:28 ` Jim Blandy
2002-11-25 5:37 ` Alexander Larsson
2002-11-25 9:44 ` 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=vt2fztxbuhg.fsf@zenia.red-bean.com \
--to=jimb@redhat.com \
--cc=alexl@redhat.com \
--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