Re: [ECOS] gdb shows incorrect source file while debugging

Re: [ECOS] gdb shows incorrect source file while debugging

[ken king]

--- Andrew Lunn <andrew@lunn.ch> wrote:
> On Tue, Apr 26, 2005 at 05:33:37PM -0700, ken king
> wrote:
> > I'm trying to port eCOS & RedBoot to a custom
> Power PC
> > (MPC852).
> > I started with the Adder sense it has a similar
> > processor an I/O.
> > I added my card to the cdl scripts, created a
> > directory and wrote a custom hal_hardware_init.
> > 
> > I'm using a BDM to download and debug, after
> > downloading I can see the reset vector (in
> assembly)
> > single stepping to another small assembly code
> > segment, but when it branches to hal_hardware_init
> --
> > gdb loads up some other source file (I think it's
> > displaying some .hxx file).
> > 
> > Looking at the registers and dumping memory around
> the
> > PC, I am running the code I wrote for
> > hal_hardware_init. I can even set breakpoints on
> my
> > label names.
> > 
> > I can copy and assemble _just_ this code module in
> > another directory and it works as expected. I even
> > changed the cdl to use -gstabs instead of -g ---no
> > luck.
> > 
> > Please tell me what I'm missing when I build with
> the
> > eCOS config tool.
> 
> But of a long shot, but try deleting your complete
> work tree and
> starting again. You might have some old symbols in
> yout libtarget.a.
> 
>         Andrew
> 
No Joy. 
Pulls up sorce code from ctype.inl and "stops" in
tolower(). But it is still really running
hal_hardware_init. This is different than yesterday,
which is really confusing.
kk

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] gdb shows incorrect source file while debugging

[Gary Thomas]

On Wed, 2005-04-27 at 11:25 -0700, ken king wrote:
> --- Andrew Lunn <andrew@lunn.ch> wrote:
> > On Tue, Apr 26, 2005 at 05:33:37PM -0700, ken king
> > wrote:
> > > I'm trying to port eCOS & RedBoot to a custom
> > Power PC
> > > (MPC852).
> > > I started with the Adder sense it has a similar
> > > processor an I/O.
> > > I added my card to the cdl scripts, created a
> > > directory and wrote a custom hal_hardware_init.
> > > 
> > > I'm using a BDM to download and debug, after
> > > downloading I can see the reset vector (in
> > assembly)
> > > single stepping to another small assembly code
> > > segment, but when it branches to hal_hardware_init
> > --
> > > gdb loads up some other source file (I think it's
> > > displaying some .hxx file).
> > > 
> > > Looking at the registers and dumping memory around
> > the
> > > PC, I am running the code I wrote for
> > > hal_hardware_init. I can even set breakpoints on
> > my
> > > label names.
> > > 
> > > I can copy and assemble _just_ this code module in
> > > another directory and it works as expected. I even
> > > changed the cdl to use -gstabs instead of -g ---no
> > > luck.
> > > 
> > > Please tell me what I'm missing when I build with
> > the
> > > eCOS config tool.
> > 
> > But of a long shot, but try deleting your complete
> > work tree and
> > starting again. You might have some old symbols in
> > yout libtarget.a.
> > 
> >         Andrew
> > 
> No Joy. 
> Pulls up sorce code from ctype.inl and "stops" in
> tolower(). But it is still really running
> hal_hardware_init. This is different than yesterday,
> which is really confusing.

These are really tool chain issues.  What version of the
various tools are you trying to use?  Have you checked with
the tool [mailing] lists, in case they have any ideas?

I've often seen this behaviour with GDB - it can get quite
confused where the sources might be if you have code or functions
that come from include files.  For the most part, one just has
to work around it.

In other words, it doesn't look like you've done anything wrong.


-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] gdb shows incorrect source file while debugging

[Andrew Lunn]

On Tue, Apr 26, 2005 at 05:33:37PM -0700, ken king wrote:
> I'm trying to port eCOS & RedBoot to a custom Power PC
> (MPC852).
> I started with the Adder sense it has a similar
> processor an I/O.
> I added my card to the cdl scripts, created a
> directory and wrote a custom hal_hardware_init.
> 
> I'm using a BDM to download and debug, after
> downloading I can see the reset vector (in assembly)
> single stepping to another small assembly code
> segment, but when it branches to hal_hardware_init --
> gdb loads up some other source file (I think it's
> displaying some .hxx file).
> 
> Looking at the registers and dumping memory around the
> PC, I am running the code I wrote for
> hal_hardware_init. I can even set breakpoints on my
> label names.
> 
> I can copy and assemble _just_ this code module in
> another directory and it works as expected. I even
> changed the cdl to use -gstabs instead of -g ---no
> luck.
> 
> Please tell me what I'm missing when I build with the
> eCOS config tool.

But of a long shot, but try deleting your complete work tree and
starting again. You might have some old symbols in yout libtarget.a.

        Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] gdb shows incorrect source file while debugging

[ken king]

I'm trying to port eCOS & RedBoot to a custom Power PC
(MPC852).
I started with the Adder sense it has a similar
processor an I/O.
I added my card to the cdl scripts, created a
directory and wrote a custom hal_hardware_init.

I'm using a BDM to download and debug, after
downloading I can see the reset vector (in assembly)
single stepping to another small assembly code
segment, but when it branches to hal_hardware_init --
gdb loads up some other source file (I think it's
displaying some .hxx file).

Looking at the registers and dumping memory around the
PC, I am running the code I wrote for
hal_hardware_init. I can even set breakpoints on my
label names.

I can copy and assemble _just_ this code module in
another directory and it works as expected. I even
changed the cdl to use -gstabs instead of -g ---no
luck.

Please tell me what I'm missing when I build with the
eCOS config tool.

Thanks for your help.
kk

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss