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, vladimir@codesourcery.com
Subject: Re: DWARF question
Date: Tue, 02 Oct 2007 19:26:00 -0000	[thread overview]
Message-ID: <47029B5B.9070002@linux.vnet.ibm.com> (raw)
In-Reply-To: <m33awtz5sy.fsf@codesourcery.com>

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



Jim Blandy wrote:
>
> I think I see the problem.  First, check this out:
>
>     (gdb) break 20
>     No line 20 in file "1s2c.c".
>     (gdb) break 10
>     Breakpoint 1 at 0x80483a1: file 1s2c.c, line 10.
>     (gdb) break 20
>     Breakpoint 2 at 0x80483c6: file 1s2c.c, line 20.
>     (gdb)
>
I can't reproduce this using my Fortran code:

    (gdb) b 31
    No line 31 in file "test-main.f".
    (gdb) b 25
    Breakpoint 1 at 0x10000670: file test-main.f, line 25.
    (gdb) b 31
    No line 31 in file "test-main.f".

But I know that line is there:

    (gdb) b ifunc
    Breakpoint 2 at 0x10000770: file test-main.f, line 30.

> As for the fix, it seems to me that if find_line_symtab can't find a
> match in the symtabs currently loaded, it should expand partial symbol
> tables with the same name as the given symtab one by one until it
> either finds one that does have the line we're looking for, or it runs
> out of plausible psymtabs to try.
>
> Even when find_line_common does return a line number, if it sets
> *exact_match is zero, I think find_line_symtab should proceed to
> expand psymtabs.  Otherwise, if the first symtab we happen to find has
> line numbers higher than the one we're looking for, but some unread
> symtab has an exact match, we'll just return the first line number in
> the symtab we've got.
Sounds reasonable to me. I'll try this.

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

iD8DBQFHAptaqvq7Aov/qQARAnZ7AKCDL8w1DdMqZzid7OzRAyvcoz+kWQCeOW37
JrS57mExOxzSTp6vi8N9iQg=
=6/rk
-----END PGP SIGNATURE-----


  reply	other threads:[~2007-10-02 19:26 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
2007-10-02 19:15               ` Jim Blandy
2007-10-02 19:26                 ` Carlos Eduardo Seo [this message]
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=47029B5B.9070002@linux.vnet.ibm.com \
    --to=cseo@linux.vnet.ibm.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=jimb@codesourcery.com \
    --cc=vladimir@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