"This is decompiled code"
Locked
 
|
Hi all. Browsing some methods, I've seen the following:
" ***This is decompiled code.*** The source was unavailable because the source pointer appears to point to an incorrect position in the file. The file may have been modified after this method was updated." This happens with some methods, the VisualWorks home directory and Parcel path are setted correctly. Should I install all the components again? Thanks. Andrea |
|
|
Andrea Gammachi wrote: > Hi all. Browsing some methods, I've seen the following: > > " ***This is decompiled code.*** > The source was unavailable because the source pointer appears to > point to an incorrect position in > the file. The file may have been modified after this method was > updated." > > This happens with some methods, the VisualWorks home directory and > Parcel path are setted correctly. > Should I install all the components again? > Thanks. That may happen when launching an image without an absolute filename path. I've had this issue when starting from desktop shortcuts (aliases) pointing to the image file on MacOS X. This way the image thinks its located in the current directory (whatever that currently is) where it can't find the change log. On Windows however, that probelm didn't occur. It seems Windows passes absolute filenames when resolving shortcuts. Apple doesn't (?) Andre |
Re: "This is decompiled code"
|
|
In reply to this post by Andrea Gammachi
What version of VW are you using?
What is $VISUALWORKS set to? Dave Andrea Gammachi wrote: > Hi all. Browsing some methods, I've seen the following: > > " ***This is decompiled code.*** > The source was unavailable because the source pointer appears to > point to an incorrect position in > the file. The file may have been modified after this method was > updated." > > This happens with some methods, the VisualWorks home directory and > Parcel path are setted correctly. > Should I install all the components again? > Thanks. > > Andrea > > |
Re: "This is decompiled code"
|
|
I'm using VisualWorks NC 7.3.1 (Patches: (none))
$(VISUALWORKS) is setted to c:\Program Files\Cincom\vw7.3.1nc The image and changes file (the real file, not the environment variable) path is C:\Program Files\Cincom\vw7.3.1nc\image\ I have another problem that could be closely related, the associaton between the file extension .im and the executable is gone, and the entry in the program files list of the "Open with..." dialog isn't added when I select the vwnc.exe. Currently I'm starting VW with a command line in the Properties dialog of the image file, both problems persists (the ***decompiled code*** and lost association) still trying to change the "Start in..." path to both ..\vw7.3.1nc\image and ..\vw7.3.1nc\bin\win I need to keep old versions of VW running, the problem appeared after I've installed VW NC 7.4 and NC 3.0, which make the association of the image with the 3.0 virtual machine (the ***This is decompiled code.*** problem doesn't happen in 3.0). In trying to fix this, I've uninstalled 7.4, but I guess some keys and values in the windows registry are causing problems. Any fix for this? cheers Andrea 2006/4/18, Dave Stevenson <[hidden email]>: What version of VW are you using? |
Re: "This is decompiled code"
|
|
If the source files are where they are expected to be, then other
possibilities are: - the source file is for a different version of VW - the source file(s) got corrupted on unzip Did you install remotely (from our server) or locally? If locally, did you have a physical CD or a mounted .iso file? If mounted .iso file, what utility did you use to mount it? Did you use the VWInstaller, or extract the .tar.gz files with some other utility? Dave Andrea Gammachi wrote: > I'm using VisualWorks NC 7.3.1 (Patches: (none)) > $(VISUALWORKS) is setted to c:\Program Files\Cincom\vw7.3.1nc > The image and changes file (the real file, not the environment variable) > path is C:\Program Files\Cincom\vw7.3.1nc\image\ > > I have another problem that could be closely related, the associaton > between the file extension .im and the executable is gone, and the entry > in the program files list of the "Open with..." dialog isn't added when > I select the vwnc.exe. > Currently I'm starting VW with a command line in the Properties dialog > of the image file, both problems persists (the ***decompiled code*** and > lost association) still trying to change the "Start in..." path to both > ..\vw7.3.1nc\image and ..\vw7.3.1nc\bin\win > > I need to keep old versions of VW running, the problem appeared after > I've installed VW NC 7.4 and NC 3.0, which make the association of the > image with the 3.0 virtual machine (the ***This is decompiled code.*** > problem doesn't happen in 3.0). In trying to fix this, I've uninstalled > 7.4, but I guess some keys and values in the windows registry are > causing problems. Any fix for this? > cheers > > Andrea > > > 2006/4/18, Dave Stevenson <[hidden email] > <mailto:[hidden email]>>: > > What version of VW are you using? > > What is $VISUALWORKS set to? > > Dave > > Andrea Gammachi wrote: > > Hi all. Browsing some methods, I've seen the following: > > > > " ***This is decompiled code.*** > > The source was unavailable because the source pointer appears to > > point to an incorrect position in > > the file. The file may have been modified after this method was > > updated." > > > > This happens with some methods, the VisualWorks home directory and > > Parcel path are setted correctly. > > Should I install all the components again? > > Thanks. > > > > Andrea > > > > > > |
|
|
In reply to this post by Andrea Gammachi
Andrea Gammachi wrote:
> I'm using VisualWorks NC 7.3.1 (Patches: (none)) > $(VISUALWORKS) is setted to c:\Program Files\Cincom\vw7.3.1nc > The image and changes file (the real file, not the environment variable) > path is C:\Program Files\Cincom\vw7.3.1nc\image\ This combination looks OK. When the VM is launched it is necessary that the working directory is set to the directory where the launched image is sitting in. [...] > > I need to keep old versions of VW running, the problem appeared after I've > installed VW NC 7.4 and NC 3.0, which make the association of the image > with the 3.0 virtual machine (the ***This is decompiled code.*** problem > doesn't happen in 3.0). In trying to fix this, I've uninstalled 7.4, but I > guess some keys and values in the windows registry are causing problems. > Any fix for this? > cheers With recent versions of VW comes a utility to launch images of any version of VW (provided you have the corresponding VM installed). I'm not sure what the installer calls it, probably something like 'image switcher' or 'image selector'. It is installed as a program called VisualWorks.exe and an .ini file (in the same directory as the exe). You will need to edit this .ini file to reflect your VW installation paths. With this utility installed you can associate .im files with the VisualWorks.exe program. It is advisable that you remove all registry keys for VW when using this utility, you can probably (I'm working from memory here) find them under hkey\local machine\software\parcplace\ and hkey\local machine\software\cincom\ HTH, Reinout ------- |
|
|
At 08:59 AM 30/04/2006, Reinout Heeck wrote:
>Andrea Gammachi wrote: >> I'm using VisualWorks NC 7.3.1 (Patches: (none)) >> $(VISUALWORKS) is setted to c:\Program Files\Cincom\vw7.3.1nc >> The image and changes file (the real file, not the environment variable) >> path is C:\Program Files\Cincom\vw7.3.1nc\image\ > >This combination looks OK. >When the VM is launched it is necessary that the working directory is set to >the directory where the launched image is sitting in. No, that shouldn't be necessary, and in Windows, depending on the version and how you launched the image, it may in fact be set to a variety of semi-random locations. -- Alan Knight [|], Cincom Smalltalk Development [hidden email] [hidden email] http://www.cincom.com/smalltalk "The Static Typing Philosophy: Make it fast. Make it right. Make it run." - Niall Ross |
Re: "This is decompiled code"
|
|
In reply to this post by Dave Stevenson-2
2006/4/24, Dave Stevenson <[hidden email]>: If the source files are where they are expected to be, then other Ok. How can I check if the source file is corrupted? Did you install remotely (from our server) or locally? I've used the VWInstaller (as I didn't found a way to download the ISO and install it locally) and installed from the server. If locally, did you have a physical CD or a mounted .iso file? Thank you. Andrea Andrea Gammachi wrote: |
Re: "This is decompiled code"
|
|
If you installed using VWInstaller, there should be files called:
$VISUALWORKS\install.log $VISUALWORKS\uninstal.log and if an error occurred there may also be a file called: $VISUALWORKS\error.log Please send them. Also, what is the exact size, in bytes, of your visual.sou file, and it's timestamp? To install directly from a downloaded .iso file, follow directions on the download site for mounting a loop device on linux, or get Daemon Tools for Win (not iso-buster), available at: <www.daemon-tools.cc> Dave Andrea Gammachi wrote: > > 2006/4/24, Dave Stevenson <[hidden email] > <mailto:[hidden email]>>: > > If the source files are where they are expected to be, then other > possibilities are: > - the source file is for a different version of VW > - the source file(s) got corrupted on unzip > > > Ok. How can I check if the source file is corrupted? > > Did you install remotely (from our server) or locally? > > > I've used the VWInstaller (as I didn't found a way to download the ISO > and install it locally) and installed from the server. > > > If locally, did you have a physical CD or a mounted .iso file? > > If mounted .iso file, what utility did you use to mount it? > > Did you use the VWInstaller, or extract the .tar.gz files with some > other utility? > > Dave > > > Thank you. > > Andrea > > Andrea Gammachi wrote: > > I'm using VisualWorks NC 7.3.1 (Patches: (none)) > > $(VISUALWORKS) is setted to c:\Program Files\Cincom\vw7.3.1nc > > The image and changes file (the real file, not the environment > variable) > > path is C:\Program Files\Cincom\vw7.3.1nc\image\ > > > > I have another problem that could be closely related, the associaton > > between the file extension .im and the executable is gone, and > the entry > > in the program files list of the "Open with..." dialog isn't > added when > > I select the vwnc.exe. > > Currently I'm starting VW with a command line in the Properties > dialog > > of the image file, both problems persists (the ***decompiled > code*** and > > lost association) still trying to change the "Start in..." path > to both > > ..\vw7.3.1nc\image and ..\vw7.3.1nc\bin\win > > > > I need to keep old versions of VW running, the problem appeared after > > I've installed VW NC 7.4 and NC 3.0, which make the association > of the > > image with the 3.0 virtual machine (the ***This is decompiled > code.*** > > problem doesn't happen in 3.0). In trying to fix this, I've > uninstalled > > 7.4, but I guess some keys and values in the windows registry are > > causing problems. Any fix for this? > > cheers > > > > Andrea > > > > > > 2006/4/18, Dave Stevenson <[hidden email] > <mailto:[hidden email]> > > <mailto:[hidden email] <mailto:[hidden email]>>>: > > > > What version of VW are you using? > > > > What is $VISUALWORKS set to? > > > > Dave > > > > Andrea Gammachi wrote: > > > Hi all. Browsing some methods, I've seen the following: > > > > > > " ***This is decompiled code.*** > > > The source was unavailable because the source pointer > appears to > > > point to an incorrect position in > > > the file. The file may have been modified after this > method was > > > updated." > > > > > > This happens with some methods, the VisualWorks home > directory and > > > Parcel path are setted correctly. > > > Should I install all the components again? > > > Thanks. > > > > > > Andrea > > > > > > > > > > > > |
«
Return to VisualWorks
|
1 view|%1 views
| Free forum by Nabble | Edit this page |