From mboxrd@z Thu Jan  1 00:00:00 1970
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 11:37:00 -0000
Message-id: <Pine.GSO.4.33.0110041134580.13231-100000@makita.cygnus.com>
References: <Pine.SGI.4.30.0110041419000.3567-100000@world.std.com>
X-SW-Source: 2001-10/msg00053.html

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