Re: Debugging modules

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

a7zulu@xxxxxxxxx wrote:
It usually means the module was relocated from the default address
(0x400000, or whatever) to the appropriate available spot in the
process' memory. You can safely ignore it for now. Relocation only
costs you some time. If you want the dynamic libraries load as fast
as possible, and you know how many your exe has, you can make them
all have different default load addresses, so there would be no
conflict. Then no relocation occurs. That's all IIRC, of course.


I was just wondering this causing me to be unable to use Visual Studio
to debug my xll code.

I don't think so.

Is there any way that I can get it not be
relocated from the default?

There is a linker option that specifies the load address for a DLL.
Take a look at the address space of the process, find a hole big enough
to contain your DLL (xll, whatever) and specify an address close to the
start of the hole as the load address. Relink. But I don't think it's
going to help.

V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask


.

Relevant Pages

  • Re: MFC71U.dll base address overlaps MSVCR71.dll
    ... DLL is already in the suggested space, it is relocated to a different space. ... relocation takes place no matter where the load address is; ... to the computed load address, whether it is the one that appears in the DLL or one that is ...
    (microsoft.public.vc.mfc)
  • Re: how do you start learning assembly language
    ... But you really ought to have a dos stub - I ... the code doesn't load at its preferred address, ... .exe goes into memory first, it always loads at 400000h, and so doesn't ... need relocation. ...
    (alt.lang.asm)
  • Re: PE to BIN
    ... The end result is a headerless flat binary file followed by a PE relocation ... one can generally just load a PE file into memory and do the relocations/... ... I would personally just assume using a plain PE/COFF image, since the fixed load address case will likely at most only add a few extra 'mov' instructions over a flat binary. ...
    (comp.lang.asm.x86)
  • Re: Do fork copies the "Code" Memory space?
    ... > 1) the relocation table is used at RUNTIME? ... > when ever process B reference the dll, ... The problem would be if the DLL was coded to load at ...
    (comp.unix.programmer)
  • Re: Debugging modules
    ... In my "modules debug window" under my xll, it is saying ... "The module did not load at the default load address" ... Then no relocation occurs. ...
    (microsoft.public.vc.language)