This is the mail archive of the gdb-patches@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: [PATCH]: memory region attributes


"J.T. Conklin" wrote:
> 
> >>>>> "Fernando" == Fernando Nasser <fnasser@redhat.com> writes:
> Fernando> You forgot to look for xfer_memory in the gdbtk subdirectory...
> Fernando> Insight does not currently build.
> 
> I'll have to check out insight before I can address this.  My first
> thought was what the hell is gdbtk doing with an xfer_memory vector
> or whatever code.  I'll refrain from making judgement until I see
> the code.
> 

OK, here is why:

Insight has its own mechanism to decide from where it is disassembling
from:
the target memory or the exec file.

The xfer_memory() call is used when it wants to make sure that the
memory position
to be disassembled comes from the exec file (not from the target
memory).

The MI does the same.


-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

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