This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: gdb & arm


On Thu, 4 Oct 2001, Quality Quorum wrote:

> It call to arm_skip_prologue call find_pc_partial_function and
> it succeeds.

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.


> My function start looks like following
>
>     mov ip, sp
>     stmdb !sp, { ...}
>     sub fp, ip, #4
> (*) <start moving data from apcs registers to locations
>      described in symbol tables>
>
>
> (*) - breakpoint goes here.

The prologues I was looking were exactly like this. I think we may be
seeing the same problem. What does readelf say for the line info?

Keith



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]