The bug is of the most trivial nature: an uninitialized pointer. Hence, the behavior is generally random and depends on the memory layout and initialization, which differs from one OS to another. This bug is fixed in version 1.1.
Thanks, Serge -----Original Message----- From: Peter Caven [mailto:[EMAIL PROTECTED]] Sent: Monday, July 22, 2002 7:51 PM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] ILASM behaves differently on Win2K and WinXP Thanks, Serge, I noticed that sentence soon after I had posted my question ... :-) I can live with stating the export name explicitly, but if it's just a bug in ILASM, then what is it about WinXP that exposes it? Andy, It's not the loader (I think) because copying the DLL from WinXP to Win2K does not correct the problem. Thanks again, -- Peter On Mon, 22 Jul 2002 09:40:07 -0700, Serge Lidin <[EMAIL PROTECTED]> wrote: >I am afraid this has nothing to do with Win2K/WinXP. It's a bug in version 1.0 of ILASM: you need to specify the export alias even if it's the same as the name of the method. The book states it explicitly: "It is necessary to specify <export name> even if the method is exported under its own name". > >Thanks, >Serge You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
