Re: [Openocd-development] How to debug a program not run at it'sruntime address

[Dominic <Dom...@gm...>]

On Tuesday 30 September 2008 08:22:20 Øyvind Harboe wrote:
> On Tue, Sep 30, 2008 at 6:14 AM, dswei <ds...@si...> wrote:
> > Thank you, Duane Ellis,
> >
> >    Yes, set the HARDWARE instruction break point may be more easy for
> > this question. But I can't still set the break point by double click on
> > the source code. For example, I have to disassemble the linux kernel
> > 'vmlinux', and find the virtual address of 'turn_on_mmu',
> > calculate the corresponding physical address. After that, I can set the
> > 'HARDWARE instruction break point'.
>
> ???
>
> I thought hardware breakpoints used the logical address??

They do, but the code at the beginning of turn_on_mmu is executing with the 
MMU turned off - after all it's that code's job to turn it on.

Duane most likely meant to place a breakpoint at some point within 
turn_on_mmu /after/ the MMU is turned on.

> >    Can I debug the program by click buttons, double click on the source
> > code , even if it's location has a constant offset to it's runtime
> > address?
>
> I don't understand this question.

I suppose he means if there's a way to tell Eclipse, DDD or Insight to 
automatically do what has to be done. I'm not sure if Eclipse supports 
placement of hardware breakpoints.

The need to calculate the address using a constant virtual->physical offset 
disappears if an address that executes with the MMU turned on gets used.

Regards,

Dominic