Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb@sourceware.org, drow@false.org
Subject: Re: DWARF question
Date: Mon, 01 Oct 2007 17:49:00 -0000	[thread overview]
Message-ID: <4701333C.9040705@linux.vnet.ibm.com> (raw)
In-Reply-To: <m34pheqt6u.fsf@codesourcery.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Jim Blandy wrote:
>
> What probably happens is that '-readnow' somehow affects the order in
> which the full symtabs get put in the list.  I'm surprised that
> breakpoints by line number in both main and the function work, but I
> guess that has something to do with the nature of the bug in
> find_line_symtab.
Here's what I got. The loop  'ALL_SYMTABS' has only one iteration
because 's->next' is NULL. So it seems that GDB isn't loading the
other symtab.

When I use '-readnow', both symtabs are there:

(top-gdb) p s->filename
$6 = 0x106a4930 "init.c"
(top-gdb) p (s->next)->filename
$7 = 0x1069cf10 "/usr/src/packages/BUILD/glibc-2.4/cc-nptl/csu/crti.S"
(top-gdb) p ((s->next)->next)->filename
$8 = 0x1069cc60 "test-main.f"
(top-gdb) p (((s->next)->next)->next)->filename
$9 = 0x1069c280 "test-main.f"
(top-gdb) p ((((s->next)->next)->next)->next)->filename
$10 = 0x1068d5c0 "crtsavres.S"
(top-gdb) p (((((s->next)->next)->next)->next)->next)->filename
$11 = 0x1068d2a0 "/usr/src/packages/BUILD/glibc-2.4/cc-nptl/csu/crtn.S"
(top-gdb) p (((((s->next)->next)->next)->next)->next)->next
$17 = (struct symtab *) 0x0

And the loop 'ALL_SYMTABS' work. So, it looks like the bug isn't in
this function. I'm going to look at where GDB populates the symtabs
list now.

Any thoughts?

Regards,

- --
Carlos Eduardo Seo
Software Engineer
IBM Linux Technology Center
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHATM8qvq7Aov/qQARAjvjAJ9gkyzimsdqWIcfomV92r2epC14RgCeIij7
aImDP4A6XiUgmIRbEnRhe+Q=
=dpf+
-----END PGP SIGNATURE-----


  reply	other threads:[~2007-10-01 17:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26 21:25 Carlos Eduardo Seo
2007-09-26 21:27 ` Daniel Jacobowitz
2007-09-27  8:29   ` Carlos Eduardo Seo
2007-09-28 20:26     ` Carlos Eduardo Seo
2007-09-28 21:13       ` Jim Blandy
2007-09-28 23:14         ` Carlos Eduardo Seo
2007-09-28 23:49           ` Jim Blandy
2007-10-01 17:49             ` Carlos Eduardo Seo [this message]
2007-10-02 19:15               ` Jim Blandy
2007-10-02 19:26                 ` Carlos Eduardo Seo
2007-10-02 21:43                 ` Carlos Eduardo Seo
2007-10-02 23:05                   ` Carlos Eduardo Seo
2007-10-02 20:03               ` Jim Blandy
2007-10-02 20:09               ` 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=4701333C.9040705@linux.vnet.ibm.com \
    --to=cseo@linux.vnet.ibm.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=jimb@codesourcery.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