Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: gdb@sources.redhat.com
Subject: dwarf2read.c:read_partial_die question
Date: Wed, 09 Jun 2004 15:42:00 -0000	[thread overview]
Message-ID: <20040609154226.GC11156@white> (raw)

Hi,

I modified read_partial_die with my -file-list-exec-source-files patch.

I have this,
   4875  case DW_AT_name:
   4876
   4877    /* Prefer DW_AT_MIPS_linkage_name over DW_AT_name.  */
   4878    if (part_die->name == NULL)
   4879      part_die->name = DW_STRING (&attr);
   4880    break;
   4881  case DW_AT_comp_dir:
   4882    if (part_die->dirname == NULL)
   4883      part_die->dirname = DW_STRING (&attr);
   4884    break;

So, the question is, part_die->name is NULL and part_die->dirname is
NULL. Is this OK? Why would the name or the dirname of the file be NULL?


This is the comment in the testcase (twice.exp) that is producing this
behavior
       # Test that GDB can still detect whether we have line numbers
       # even if we're executing code in an include file.

This is what the dwarf2 spec says,
   A DW_AT_comp_dir attribute whose value is a null-terminated string
   containing the current
   working directory of the compilation command that produced this
   compilation unit in
   whatever form makes sense for the host system.
   The suggested form for the value of the DW_AT_comp_dir attribute on
   UNIX systems is
   hostname:pathname. If no hostname is available, the suggested form is
   :pathname.

Basically, it doens't say anything about it being NULL.

So, what I want to know is, is it valid that the value of part_die->dirname is
NULL and that the value of part_die->name is NULL?

Thanks,
Bob Rossi


             reply	other threads:[~2004-06-09 15:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 15:42 Bob Rossi [this message]
2004-06-09 15:45 ` Daniel Jacobowitz
2004-06-09 16:06   ` Bob Rossi
2004-06-09 17:04     ` Daniel Jacobowitz
2004-06-09 17:58       ` Bob Rossi

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=20040609154226.GC11156@white \
    --to=bob@brasko.net \
    --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