Subject:Re: access violation - log file attached Author:Minollo I. Date:29 Aug 2001 09:51 AM
At 06:53 AM 8/29/2001 -0400, you wrote:
>From: "Martin Roberts"
>
>This has occurred again when I tried to change the file being processed in
>an xslt scenario.
You mean, same log file, with an empty stack trace at the bottom?
I have tried it with both a new xslt sheet and a new scenario file. One step I failed to mention is that the file is not a .xml file so I have to use the all files option.
Subject:Re: access violation - log file attached Author:Minollo I. Date:04 Sep 2001 11:18 AM
: "Martin Roberts"
>
>I have tried it with both a new xslt sheet and a new scenario file. One
>step I failed to mention is that the file is not a .xml file so I have to
>use the all files option.
Ok, we think we understand the problem; we can reproduce it if in the
scenario dialog we select a file which is not .xml and whose custom
extension has been associated to anything different from the XMLEditor plugin.
We have fixed that case; you shouldn't experience that access violation
anymore in beta 2 (available today or tomorrow).
I can now confirm that the scenario that causes this is as follows:
1) Start Stylus
2) Open XSL sheet with scenario already defined
3) Click ... box next to scenario name
4) Change the file name of the file to be processed or create another scenario
5) press OK and BANG! off goes the access violation
>...
>I can now confirm that the scenario that causes this is as follows:
>
>1) Start Stylus
>2) Open XSL sheet with scenario already defined
>3) Click ... box next to scenario name
>4) Change the file name of the file to be processed or create another scenario
>5) press OK and BANG! off goes the access violation
I can't reproduce that; are you sure it's not related to the file you are
choosing in step #4? Have tried running the same steps using a different
scenario file in #4?
Subject:Re: access violation - log file attached Author:Minollo I. Date:05 Sep 2001 08:40 AM
At 04:52 AM 9/5/2001 -0400, you wrote:
>From: "Martin Roberts"
>
>Still occurring in studio 3.1.59 build
>
>I don't know if the message got to you:
>
>I did one extra step which was to change the *.xml to *.* in the open file
>dialog. I do not know if this causes the problem
Yes, we got the message; in our tests we were able to reproduce the crash
switching to *.* and then opening a non-XML file, or a file whose extension
had not been associated to the XML Editor in Stylus Studio.
Can you double check that you are running 59a opening the About dialog (in
some cases we have noticed that IE5 tends to cache the FTP and HTTP packages)?
If it actually is 59a, can you tell me:
- what is the extension of the file you are selecting after switching to
the *.* filter?
- what is the content of the file? Is it XML?
- what does it happen if you open Stylus Studio and just open that same
file? Which editor opens it?
Subject:Re: access violation - log file attached Author:Minollo I. Date:06 Sep 2001 10:59 AM
FYI.
We have worked off-line with Martin to understand this issue.
Turns out to be a problem with some missing clean-up in the upgrade path
from older builds to BL59; we have some suspect in the registry area, and
we are still investigating.
In the meanwhile, if you experience similar issues, you may want to try
closing the application, removing this registry entry
"HKEY_CURRENT_USER\Software\eXcelon Corporation\Stylus Studio", and
restarting the application..