Here is a quick tutorial ... http://codebetter.com/blogs/gregyoung/archive/2006/06/09/146298.aspx
the other method is to do this then .. in the immeiate window. .load SOS !Name2EE your.dll namespace.class.method !u addressyougetbackfrompreviouscommand On 10/5/06, gregory young <[EMAIL PROTECTED]> wrote:
Are you familiar with SOS? could you issue a !u (disassemble) on a simple method that shows this problem and post the native code to the group? I don't have a 64 bit machine here to test on. Cheers, Greg On 10/5/06, Stanislav Peťko <[EMAIL PROTECTED]> wrote: > Hello. > > We have troubles with development on x64 machine. This machine si Athlon x64, with Windows XP x64 installed, .NET Frameworik 2.0 x64 and Visual Studio 2005 Professional. The other machine is general 32bit Athlon, Windows XP, .NET Framework 2.0 and the same Visual Studio. > > In a very simple project, we have this piece of code: > > > If e.Value.ToString = "m" Then > e.DisplayText = "male" > Else > e.DisplayText = "female" > End If > > > It happens, that e.Value is Nothing (null), so it should be raised NullReferenceException on 1st line. On 32 bit machine, everything is OK, NullReferenceException is thrown, and the project is stopped on that line. But on 64 bit machine, the exception is not thrown, program jupms to the end of method containing the code and CONTINUES! Of course, after that program acts very strange, because something wrong happened. > > The worst thing is, developer using this machine cannot work properly, when project does not raise exceptions, just goes on but strangely. > > > Did anybody meet this problem? Are we missing something in configuration, or it is some bug? > > > Thanks, Stano > > =================================== > This list is hosted by DevelopMentor� http://www.develop.com > > View archives and manage your subscription(s) at http://discuss.develop.com > -- If knowledge can create problems, it is not through ignorance that we can solve them. Isaac Asimov
-- If knowledge can create problems, it is not through ignorance that we can solve them. Isaac Asimov
