Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] build-id .debug files load (like .gnu_debuglink)
Date: Sat, 25 Aug 2007 22:48:00 -0000	[thread overview]
Message-ID: <20070825224807.ED6734D0555@magilla.localdomain> (raw)
In-Reply-To: Jan Kratochvil's message of  Friday, 24 August 2007 20:04:50 +0200 <20070824180450.GA4216@host0.dyn.jankratochvil.net>

> This part may be questionable:
> -  debugfile = find_separate_debug_file (objfile); 
> +  /* If the file has its own symbol tables it has no separate debug info.  */
> +  if (objfile->psymtabs == NULL)
> +    debugfile = find_separate_debug_file (objfile);

As Daniel mentioned, this is certainly not correct.  The main file might
have a symbol table, but not have any debug info (i.e. DWARF sections).
The condition I would use is the direct one: if the main file has no DWARF
sections, then look for a separate debug file.

> So far .gnu_debuglink existed only in the main file (not the .debug file) and
> it existed only if the debug info was stripped to a separate file from it.

This is still true.  It's not entirely unreasonable to use presence of
.gnu_debuglink as the sign that you should look for separate debug info,
even if for the actual searching you ignore its contents when you have a
build ID note.


Thanks,
Roland


      parent reply	other threads:[~2007-08-25 22:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24 18:05 Jan Kratochvil
2007-08-24 18:20 ` Daniel Jacobowitz
2007-08-25 22:49   ` Jan Kratochvil
2007-08-25 23:58     ` Daniel Jacobowitz
2007-08-26  9:41       ` Jan Kratochvil
2007-08-31  9:38         ` Eli Zaretskii
2007-08-31 20:51           ` [patch approval?] " Jan Kratochvil
2007-08-31 21:12             ` Daniel Jacobowitz
2007-09-01  8:01             ` Eli Zaretskii
     [not found]           ` <20070901081934.GA31205@host0.dyn.jankratochvil.net>
2007-09-01 10:31             ` [patch] " Eli Zaretskii
2007-09-01 11:35               ` Jan Kratochvil
2007-09-01 12:15                 ` Eli Zaretskii
2007-09-01 13:12                   ` Jan Kratochvil
2007-09-01 13:25                     ` Mark Kettenis
2007-09-01 14:22                       ` Eli Zaretskii
2007-09-02 13:57                       ` [patch approved?] [doc] " Jan Kratochvil
2007-09-02 17:49                         ` Mark Kettenis
2007-09-02 19:38                         ` Eli Zaretskii
2007-09-01 14:16                     ` [patch] " Eli Zaretskii
2007-09-04  2:21                   ` Roland McGrath
2007-09-04  3:23                     ` Eli Zaretskii
2007-09-04  7:21                       ` Roland McGrath
2007-09-15  9:52                         ` Eli Zaretskii
2007-09-16 17:19                           ` Roland McGrath
2007-08-25 22:48 ` Roland McGrath [this message]

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=20070825224807.ED6734D0555@magilla.localdomain \
    --to=roland@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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