From: Daniel Jacobowitz <drow@false.org>
To: David Lecomber <david@streamline-computing.com>
Cc: patches <gdb-patches@sources.redhat.com>
Subject: Re: [PATCH/RFA] buildsym.c: extend parent block bounds if child block exceed limit
Date: Tue, 14 Sep 2004 21:04:00 -0000 [thread overview]
Message-ID: <20040914210452.GA19646@nevyn.them.org> (raw)
In-Reply-To: <1091826690.3932.33.camel@localhost>
On Fri, Aug 06, 2004 at 10:11:30PM +0100, David Lecomber wrote:
> All,
>
> f90 compiled with nested subroutines using Intel's compiler is handled
> badly by GDB. Line numbers are not found by backtrace.
>
> Although GDB is capable of reading out all the dwarf2 line information
> inside this routine correctly, it can't look up an address to get a line
> number when inside a block. The cause is that the containing function's
> block does not contain the contained function's address.
Could you post the output of readelf -wil on this binary?
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-09-14 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 21:10 David Lecomber
2004-09-14 20:00 ` Andrew Cagney
2004-09-14 20:57 ` David Lecomber
2004-09-14 21:01 ` Michael Chastain
2004-09-14 21:04 ` Daniel Jacobowitz [this message]
2004-09-14 21:21 ` David Lecomber
2004-09-20 21:30 ` 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=20040914210452.GA19646@nevyn.them.org \
--to=drow@false.org \
--cc=david@streamline-computing.com \
--cc=gdb-patches@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