This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: gdb & arm
- To: Quality Quorum <qqi at world dot std dot com>
- Subject: Re: gdb & arm
- From: Keith Seitz <keiths at cygnus dot com>
- Date: Thu, 4 Oct 2001 15:00:44 -0700 (PDT)
- cc: <gdb at sources dot redhat dot 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