Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@cygnus.com>
To: Quality Quorum <qqi@world.std.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: gdb & arm
Date: Thu, 04 Oct 2001 15:00:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.33.0110041459120.13231-100000@makita.cygnus.com> (raw)
In-Reply-To: <Pine.SGI.4.30.0110041624380.2817-100000@world.std.com>

On Thu, 4 Oct 2001, Quality Quorum wrote:

> > So:
> >
> >   if (find_pc_partial_function (pc, NULL, &func_addr, &func_end))
> >     {
> >       sal = find_pc_line (func_addr, 0);
> >       if ((sal.line != 0) && (sal.end < func_end))
> >         return sal.end;
> >     }
> >
> > find_pc_partial_function and find_pc_line succeed, but sal.end=func_end,
> > right? This is the problem I had. Line table problems from gcc was my
> > determination.
>
> ???? I do not understand you, sal.end contains a value pointed by (*)
> below. I suppose it is a correct behavior.

What does "p/x sal.end" and "p/x func_end" give?

> I am working with arm-aout and arm-aout-readelf  was built but it does
> not like file format. Can use objdump for the purpose ?
>

Yes, even better! If you're using stabs, by all means use objdump: it's
much easier (for me, at least) to parse objdump than dwarf2 lineinfo.

Keith



  reply	other threads:[~2001-10-04 15:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-04  9:01 Quality Quorum
2001-10-04  9:13 ` Keith Seitz
2001-10-04 11:32   ` Quality Quorum
2001-10-04 11:37     ` Keith Seitz
2001-10-04 13:31       ` Quality Quorum
2001-10-04 15:00         ` Keith Seitz [this message]
2001-10-04 16:08           ` Quality Quorum
2001-10-05  9:37       ` Fernando Nasser

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=Pine.GSO.4.33.0110041459120.13231-100000@makita.cygnus.com \
    --to=keiths@cygnus.com \
    --cc=gdb@sources.redhat.com \
    --cc=qqi@world.std.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