VMTRAP.LOG location

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

VMTRAP.LOG location

Steven LaFavor
Here's my problem:

I've got a production application written in what I believe is version 4.5 or 5.0 of VAST.
It is run by the users off of a corporate network drive that is read only, and the application is started using a windows command file that changes directory to the network location, and invokes nodialog.exe with the -i parameter.

Now under Windows 7, we are seeing that the app terminates unexpectedly on rare occasions.

The first thing that I would look for is the VMTRAP.LOG file to see what was going on, but since that directory is read only, it would not be generated there.  

Does anyone know where the VMTRAP.LOG file would be created in this instance (if at all)?

And for the followup, is there a way to set where the VMTRAP.LOG file would be created via a command line switch?  Does it work off of the -l switch?

*Steve*


--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/oB7gbUCR6XsJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.
Reply | Threaded
Open this post in threaded view
|

Re: VMTRAP.LOG location

John O'Keefe-3
Steve -
 
The VMTRAP.LOG is written to the 'current directory'. This is usually the directory where the image (.icx) file is located, but can be somewhere else depending on how your startup script works.
 
John

On Thursday, January 17, 2013 1:15:08 PM UTC-5, Steven LaFavor wrote:
Here's my problem:

I've got a production application written in what I believe is version 4.5 or 5.0 of VAST.
It is run by the users off of a corporate network drive that is read only, and the application is started using a windows command file that changes directory to the network location, and invokes nodialog.exe with the -i parameter.

Now under Windows 7, we are seeing that the app terminates unexpectedly on rare occasions.

The first thing that I would look for is the VMTRAP.LOG file to see what was going on, but since that directory is read only, it would not be generated there.  

Does anyone know where the VMTRAP.LOG file would be created in this instance (if at all)?

And for the followup, is there a way to set where the VMTRAP.LOG file would be created via a command line switch?  Does it work off of the -l switch?

*Steve*


--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/RG8y-BZLDp8J.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.
Reply | Threaded
Open this post in threaded view
|

Re: VMTRAP.LOG location

Wayne Johnston
In reply to this post by Steven LaFavor
One of the headaches with Windows 7 is the "VirtualStore" which is a mystery to me.  It sure would be nice if writing a file either succeeded or failed.  With Windows 7, there is this other alternative result - "writing succeeds but the file went somewhere else".  My virtual store directory is
C:\Users\userID\AppData\Local\VirtualStore
and I sometimes go there to see if something has been written there, which is pretty much a sign of a problem.

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/t8Dlq_g3iuYJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.
Reply | Threaded
Open this post in threaded view
|

Re: VMTRAP.LOG location

Steven LaFavor
In reply to this post by John O'Keefe-3
The batch script that runs this goes something like this:
@echo off
G:
CD \
CD \myapp
START G:\myapp\myapp.exe -iU:\myapp\myapp.img
EXIT

Now the G: drive is read only, and this drive is where this script is.  Where would the VMTRAP.LOG file be written in this scenario?  Would it be written at all?  Is there a way to modify where the VMTRAP.LOG file gets created?


On Thursday, January 17, 2013 2:39:22 PM UTC-5, John O'Keefe wrote:
Steve -
 
The VMTRAP.LOG is written to the 'current directory'. This is usually the directory where the image (.icx) file is located, but can be somewhere else depending on how your startup script works.
 
John

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/ytS1ff7ks18J.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.
Reply | Threaded
Open this post in threaded view
|

Re: VMTRAP.LOG location

Steven LaFavor
In reply to this post by John O'Keefe-3
The batch script that runs this goes something like this:
@echo off
G:
CD \
CD \myapp
START G:\myapp\myapp.exe -iG:\myapp\myapp.img
EXIT

Now the G: drive is read only, and this drive is where this script is.  Where would the VMTRAP.LOG file be written in this scenario?  Would it be written at all?  Is there a way to modify where the VMTRAP.LOG file gets created?


On Thursday, January 17, 2013 2:39:22 PM UTC-5, John O'Keefe wrote:
Steve -
 
The VMTRAP.LOG is written to the 'current directory'. This is usually the directory where the image (.icx) file is located, but can be somewhere else depending on how your startup script works.
 
John

On Thursday, January 17, 2013 1:15:08 PM UTC-5, Steven LaFavor wrote:
Here's my problem:

I've got a production application written in what I believe is version 4.5 or 5.0 of VAST.
It is run by the users off of a corporate network drive that is read only, and the application is started using a windows command file that changes directory to the network location, and invokes nodialog.exe with the -i parameter.

Now under Windows 7, we are seeing that the app terminates unexpectedly on rare occasions.

The first thing that I would look for is the VMTRAP.LOG file to see what was going on, but since that directory is read only, it would not be generated there.  

Does anyone know where the VMTRAP.LOG file would be created in this instance (if at all)?

And for the followup, is there a way to set where the VMTRAP.LOG file would be created via a command line switch?  Does it work off of the -l switch?

*Steve*


--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/J23aUghIFj4J.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.
Reply | Threaded
Open this post in threaded view
|

Re: VMTRAP.LOG location

Steven LaFavor
In reply to this post by Wayne Johnston
Hmm.  Checked there as well, and looked up what the VirtualStore directory is - seems to be the place where stuff gets written if you try to write something in a location that UAC won't let you.

Wasn't there :(

On Thursday, January 17, 2013 3:25:58 PM UTC-5, Wayne Johnston wrote:
One of the headaches with Windows 7 is the "VirtualStore" which is a mystery to me.  It sure would be nice if writing a file either succeeded or failed.  With Windows 7, there is this other alternative result - "writing succeeds but the file went somewhere else".  My virtual store directory is
C:\Users\userID\AppData\Local\VirtualStore
and I sometimes go there to see if something has been written there, which is pretty much a sign of a problem.

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/va-smalltalk/-/pbMTPAtHsSEJ.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.
Reply | Threaded
Open this post in threaded view
|

Re: VMTRAP.LOG location

Steven LaFavor
In reply to this post by Steven LaFavor

Does anyone have the answers to these questions?

On Thursday, January 17, 2013 5:16:22 PM UTC-5, Steven LaFavor wrote:
Now the G: drive is read only, and this drive is where this script is.  Where would the VMTRAP.LOG file be written in this scenario?  Would it be written at all?  Is there a way to modify where the VMTRAP.LOG file gets created?

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/va-smalltalk?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: VMTRAP.LOG location

John O'Keefe-3
In reply to this post by Steven LaFavor
Steven -
 
If the current directory cannot be written to, the code that writes the vmtrap.log and vmtrap.img gives up and write nothing. So you need to set the current directory to a writeable location in your Smalltalk code using something like CfsDirectoryDescriptor chdir: 'C:\myWriteableDir'.
 
I'm not going to attempt to explain why VirtualStore does/doesn't work since I've never seen an understandable description of it -- all I know is that sometimes (seems random to me) Windows will decide to write something there.
 
John

On Thursday, January 17, 2013 5:16:22 PM UTC-5, Steven LaFavor wrote:
The batch script that runs this goes something like this:
@echo off
G:
CD \
CD \myapp
START G:\myapp\myapp.exe -iG:\myapp\myapp.img
EXIT

Now the G: drive is read only, and this drive is where this script is.  Where would the VMTRAP.LOG file be written in this scenario?  Would it be written at all?  Is there a way to modify where the VMTRAP.LOG file gets created?


On Thursday, January 17, 2013 2:39:22 PM UTC-5, John O'Keefe wrote:
Steve -
 
The VMTRAP.LOG is written to the 'current directory'. This is usually the directory where the image (.icx) file is located, but can be somewhere else depending on how your startup script works.
 
John

On Thursday, January 17, 2013 1:15:08 PM UTC-5, Steven LaFavor wrote:
Here's my problem:

I've got a production application written in what I believe is version 4.5 or 5.0 of VAST.
It is run by the users off of a corporate network drive that is read only, and the application is started using a windows command file that changes directory to the network location, and invokes nodialog.exe with the -i parameter.

Now under Windows 7, we are seeing that the app terminates unexpectedly on rare occasions.

The first thing that I would look for is the VMTRAP.LOG file to see what was going on, but since that directory is read only, it would not be generated there.  

Does anyone know where the VMTRAP.LOG file would be created in this instance (if at all)?

And for the followup, is there a way to set where the VMTRAP.LOG file would be created via a command line switch?  Does it work off of the -l switch?

*Steve*


--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To post to this group, send email to [hidden email].
To unsubscribe from this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/va-smalltalk?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.