Re: (forte-users) access violation caught in debugmode
Eric,
There has been a problem with Forte debug mode for sometime now when the app
is silent. If you attempt to inspect the variables when the app is in the
'silent' mode, i.e., waiting on an event loop for a user input or a system
event, then you get the "Access violation caught ..." exception message and
the workspace including the launch server crashes.
If you are getting this problem in the 'step-through' mode, you should look
at the lauch server immediately after you get the exception before
everything disappears. There could be a stack backtrace due to some illegal
reference. We have faced a similar situation before but the error appeared
both in the 'debug' and 'run' modes.
Hope this helps.
Braja K Chattaraj.
From: Eric Decossaux <[email protected]>
To: forte mailing <[email protected]>
Subject: (forte-users) access violation caught in debug mode
Date: Thu, 23 Sep 1999 17:31:39 +0200
Hello,
I have a problem using Forte in debug mode. If I run my program on my NT
machine from the partition workshop (distributed run), the program works
fine except that some object does not display what I'm expecting. So I
want to use the debug mode to inspect the objets of this window. When I
choose the "local variables" option to see the content of my window, I
have a "access violation caught" and forte disappears. If I just let my
program run without choosing this option, everything is the same than
with the distributed run.
Does somebody have an idea what to look for ? I really want to look the
inside the attributes of this window.
We recently upgraded from release 30G2 to release 30L2. Could it be the
problem ?
Eric Decossaux
Cliniques Universitaires St Luc
Informatique des Laboratoires
av Hippocrate 10 / 1730
1200 Bruxelles
+32+2+764 17 53
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]
Eric,
Another possibility has to do with the repository. You said you recently
migrated 30G2 to release 30L2.
Many strange problems have been traced to release migrations with old
repositories. If the repository was properly migrated another thing you can try
is to export the project(s) to PEX files, delete them from the repository, and
then re-import. I know this can be time consuming but I have solved more than
one unexplained problem in the IDE by doing it.
---------------------- Forwarded by Charlie Shell/Bsg/MetLife/US on 09/23/99
01:19 PM ---------------------------
"Ajith Kallambella" <[email protected]> on 09/23/99 12:08:54 PM
To: [email protected], [email protected]
cc: (bcc: Charlie Shell/Bsg/MetLife/US)
Subject: Re: (forte-users) access violation caught in debug mode
Eric,
Sometimes( 90% ) you can solve this problem by
checking out the class that is causing the crash
and force-compiling it.
If it doesn't help, run through this checklist.
1. Do you have enough memory resources.?
2. Is the object you are inspecting held in a lock ?
( mutex, transaction lock etc )
3. Does it work when you wait for sometime at the
breakpoint before inspecting the values? I mean
are you interrupting some process thread?
4. Does it work if you log the attributes using logmgr?
5. Are you using any call-outs/call-ins? Any external
systems integration? Sometimes( for reasons beyond
my comprehension ) the objects allocated outside
Forte gets corrupted when its passed back and forth.
6. ...finally...Santa Clause, help me!
Ajith Kallambella M.
Forte Systems Consultant.
From: Eric Decossaux <[email protected]>
To: forte mailing <[email protected]>
Subject: (forte-users) access violation caught in debug mode
Date: Thu, 23 Sep 1999 17:31:39 +0200
Hello,
I have a problem using Forte in debug mode. If I run my program on my NT
machine from the partition workshop (distributed run), the program works
fine except that some object does not display what I'm expecting. So I
want to use the debug mode to inspect the objets of this window. When I
choose the "local variables" option to see the content of my window, I
have a "access violation caught" and forte disappears. If I just let my
program run without choosing this option, everything is the same than
with the distributed run.
Does somebody have an idea what to look for ? I really want to look the
inside the attributes of this window.
We recently upgraded from release 30G2 to release 30L2. Could it be the
problem ?
Eric Decossaux
Cliniques Universitaires St Luc
Informatique des Laboratoires
av Hippocrate 10 / 1730
1200 Bruxelles
+32+2+764 17 53
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]
Similar Messages
-
Re: (forte-users) Accessing Technote 10398
Ketie,
let's see, I have been using FORTE since November of
1994. since the beginning those flags have been common
knowledge within the FORTE community and widely
disseminated.
the FORTE flags have been invaluable to me and HAVE
NEVER caused any downtime. sure, there are a few
wildcards in there that can cause trouble, but to
throw out the baby with the bathwater is ridiculous.
what would life be without trc:lo:25? to trace
exceptions.
or trc:os:1:1 and trc:os:5:5 to tune memory
consumption?
Should i have to call a consultant or FORTE tech
support to do the deep dive on exceptions or tune my
applications? I think not.
Overreaction? No.
Mark.
--- Katie Tierney <katiethetierneys.com> wrote:
I think y'all are overreacting. There are log flags
that are detailed in
Technote 10398 that can cause serious implications
if used improperly. I
think Forte/Sun just wants to make sure that people
don't make mistakes that
cost them valuable time.
As a Forte Consultant for many years, I have seen a
good number of people
misuse information that was not completely
understood. In some cases, this
caused excessive downtime for production
applications. The only time I ever
saw Technote 10398 being provided to a customer was
when they were utilizing
Forte Consulting, or when a Technical Support
Engineer was heavily involved.
I was extremely surprised to learn that it was
available to non-employees via
the website - that sounds as if someone may have
inadvertantly marked it as
customer-viewable (incorrectly, obviously) in Sun's
internal systems.
Again, I think you're overreacting. I am sure that
this isn't a case of Sun
thinking anyone is "stupid." It's a matter of
providing the support that
people need to properly utilize the tools available.
-Katie
mark joyce wrote:
read: Sometimes, the technotes are markedunviewable
to customers because they might need further
explanation. Let me know if you need to log acase.
in other words, you are TOO STUPID to use FORTElogger
flags, although they have been widely distributedand
used for years by FORTE users.
i can't believe it either. i don't know what iwould
have done for the last 5 years without using theFORTE
flags. such a wealth of good output!
what an excuse! "they might need furtherexplanation"
.. if i had to log every problem with FORTE,instead
of resolving them myself through the information
obtained by using flags, i would have lost my joba
long time ago.
mark.
--- Jeff Bennett <jeff_bennettsehamerica.com>wrote:
I thought it might be prudent to share with youthe
response I received from Sun
regarding the inability to access technote 10398
(Forté logger flags). I was
able to access it 3+ weeks ago, and fortunatelykept
a hard-copy. But, how are
we supposed to do our job effectively and
expediently if we do not have
(complete) access to this resource?
I thought the technotes were completely open tothe
Forté development
community.... wrong.
-jeff
---------------------- Forwarded by JeffBennett/SEH
on 09/11/2000 09:02 AM
Forte Support <supportforte.com> on 09/08/2000
10:05:17 AM
To: Jeff Bennett/SEHsehamerica.com
cc:
Subject: Re: Accessing Technote 10398
Fax to:
Hello Jeff,
Were you at one point able to access thistechnote?
You know why -- it's
because this technote is marked for employeeviewing
only and not available
for customer viewing. If you need further
assistance or need to look at
this technote, what you would need to do is loga
call with us and then a
tech support specialist will give you a callback.
Sometimes, the
technotes are marked unviewable to customersbecause
they might need
further explanation. Let me know if you need tolog
a case.
Thanks!
At 09:57 AM 9/8/00 -0700, you wrote:
I am no longer able to access technote 10398
(forte
logger flags)... why?
-jeff~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
Sun® microsystems
Jeannie Lee
Phone: (510) 451-5400
Fax (510) 869-2010
Email: jeannie.leesun.com
Forte Tools Response Coordinator
For the archives, go to:
http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To
unsubscribe, send in a new
email the word: 'Unsubscribe' to:
forte-users-requestlists.xpedior.com
http://mail.yahoo.com/
For the archives, go to:
http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. Tounsubscribe, send in a new
email the word: 'Unsubscribe' to:forte-users-requestlists.xpedior.com
http://mail.yahoo.com/Ketie,
let's see, I have been using FORTE since November of
1994. since the beginning those flags have been common
knowledge within the FORTE community and widely
disseminated.
the FORTE flags have been invaluable to me and HAVE
NEVER caused any downtime. sure, there are a few
wildcards in there that can cause trouble, but to
throw out the baby with the bathwater is ridiculous.
what would life be without trc:lo:25? to trace
exceptions.
or trc:os:1:1 and trc:os:5:5 to tune memory
consumption?
Should i have to call a consultant or FORTE tech
support to do the deep dive on exceptions or tune my
applications? I think not.
Overreaction? No.
Mark.
--- Katie Tierney <katiethetierneys.com> wrote:
I think y'all are overreacting. There are log flags
that are detailed in
Technote 10398 that can cause serious implications
if used improperly. I
think Forte/Sun just wants to make sure that people
don't make mistakes that
cost them valuable time.
As a Forte Consultant for many years, I have seen a
good number of people
misuse information that was not completely
understood. In some cases, this
caused excessive downtime for production
applications. The only time I ever
saw Technote 10398 being provided to a customer was
when they were utilizing
Forte Consulting, or when a Technical Support
Engineer was heavily involved.
I was extremely surprised to learn that it was
available to non-employees via
the website - that sounds as if someone may have
inadvertantly marked it as
customer-viewable (incorrectly, obviously) in Sun's
internal systems.
Again, I think you're overreacting. I am sure that
this isn't a case of Sun
thinking anyone is "stupid." It's a matter of
providing the support that
people need to properly utilize the tools available.
-Katie
mark joyce wrote:
read: Sometimes, the technotes are markedunviewable
to customers because they might need further
explanation. Let me know if you need to log acase.
in other words, you are TOO STUPID to use FORTElogger
flags, although they have been widely distributedand
used for years by FORTE users.
i can't believe it either. i don't know what iwould
have done for the last 5 years without using theFORTE
flags. such a wealth of good output!
what an excuse! "they might need furtherexplanation"
.. if i had to log every problem with FORTE,instead
of resolving them myself through the information
obtained by using flags, i would have lost my joba
long time ago.
mark.
--- Jeff Bennett <jeff_bennettsehamerica.com>wrote:
I thought it might be prudent to share with youthe
response I received from Sun
regarding the inability to access technote 10398
(Forté logger flags). I was
able to access it 3+ weeks ago, and fortunatelykept
a hard-copy. But, how are
we supposed to do our job effectively and
expediently if we do not have
(complete) access to this resource?
I thought the technotes were completely open tothe
Forté development
community.... wrong.
-jeff
---------------------- Forwarded by JeffBennett/SEH
on 09/11/2000 09:02 AM
Forte Support <supportforte.com> on 09/08/2000
10:05:17 AM
To: Jeff Bennett/SEHsehamerica.com
cc:
Subject: Re: Accessing Technote 10398
Fax to:
Hello Jeff,
Were you at one point able to access thistechnote?
You know why -- it's
because this technote is marked for employeeviewing
only and not available
for customer viewing. If you need further
assistance or need to look at
this technote, what you would need to do is loga
call with us and then a
tech support specialist will give you a callback.
Sometimes, the
technotes are marked unviewable to customersbecause
they might need
further explanation. Let me know if you need tolog
a case.
Thanks!
At 09:57 AM 9/8/00 -0700, you wrote:
I am no longer able to access technote 10398
(forte
logger flags)... why?
-jeff~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
Sun® microsystems
Jeannie Lee
Phone: (510) 451-5400
Fax (510) 869-2010
Email: jeannie.leesun.com
Forte Tools Response Coordinator
For the archives, go to:
http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To
unsubscribe, send in a new
email the word: 'Unsubscribe' to:
forte-users-requestlists.xpedior.com
http://mail.yahoo.com/
For the archives, go to:
http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. Tounsubscribe, send in a new
email the word: 'Unsubscribe' to:forte-users-requestlists.xpedior.com
http://mail.yahoo.com/ -
Re: (forte-users) systemexception
Hi There
Segmentation violations can be caused by different
situations. Force compiling works well in clearing
most SV's. It is advisable to first clear all
breakpoints, force-compile your plans and run your
application. If you still get the SV then run in debug
mode to identify the problem area.
Hope this helps.
Jairaj Rampershad
System Consultant
--- Forte App <[email protected]> wrote:
Hi,
iam getting system segmentation/access violation
Fatal Error: system segmentation/access violation
caught.
Class: qqos_SystemException
Error: [101, 321]
Detected: qqos_MainSingHd1 on part5,
Error: TMgr
RunThread:task10.SAsync.AppServerInterfaceMgr
Error:qq10_LomTaskInitiator
what cause this type of error
Thanks in advance
For the archives, go to:
http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To
unsubscribe, send in a new
email the word: 'Unsubscribe' to:
[email protected]Hi Jean-Paul,
As described in the Technote 10981 some Forte programs (Nodemanager and
router) handle correct the high-file descriptor-use problem. It is possible
that Forte interpreter do it correct too.
Zenon
-----Original Message-----
From: Jean-Paul Gabrielli [SMTP:Jean-Paul.Gabriellisema.fr]
Sent: Monday, September 25, 2000 12:11 PM
To: Adamek, Zenon
Cc: Forte-userslists.xpedior.com
Subject: RE: (forte-users) [UNIX] "Too many open files" 3.0.M2
question
Actually, the stuff works in interpreted mode.
It's only when having the server partition compiled that this happen.
j-p
-----Message d'origine-----
De: Adamek, Zenon [mailto:ZAdamekpurolator.com]
Date: lundi 25 septembre 2000 17:13
À: 'Jean-Paul.Gabriellisema.fr'
Cc: Forte-userslists.xpedior.com
Objet: RE: (forte-users) [UNIX] "Too many open files" 3.0.M2 question
see Technote 10981
-----Original Message-----
From: Jean-Paul Gabrielli [SMTP:Jean-Paul.Gabriellisema.fr]
Sent: Monday, September 25, 2000 11:02 AM
To: zeForte-users
Subject: (forte-users) [UNIX] "Too many open files" 3.0.M2 question
Hi,
running a server partition that reads a configuration file,
and apparently doen't close it after, I have that exception:
SYSTEM ERROR: System Error: Too many open files, opening '....'with mode
'r'
Class: qqos_FileResourceException
1) Is there such a limit, or does this rely only on the OS one ?
2) How is this error not trapped, as I only got itinteractively, whereas
my server log does a exception trap/segmentation fault,
thanlks
j-p
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe,send in a new
email the word: 'Unsubscribe' to:
forte-users-requestlists.xpedior.com
>
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com -
RE: (forte-users) SerializationException
Ravi,
Are your partitions compiled?
On comiled partitions, NIL object exceptions show
up as these.
Hope this helps.
Nirmal
Nirmal P Uppalapati Phone:
(203) 622-5386
VP-US Operations
(203)
359-3992
PSI Data Systems Ltd. Mobile:
(203) 829-7741
Suite 406
Fax: (203) 359-4662
One Bank Street mail :
nirmalpsidata.com
Stamford, CT 06901 USA Web:
http://www.psi.soft.net
-----Original Message-----
From: Ravindra Kallamadi
[SMTP:rkallamadiyahoo.com]
Sent: Wednesday, January 26, 2000 6:12 PM
To: kamranaminyahoo.com
Cc: William.K.Bhattapmusa.com
Subject: (forte-users) SerializationException
Has anyone experienced the following
SerializationException?
Thu Jan 20 22:33:31 : End of Stack Backtrace
Thu Jan 20 22:33:31 : THROW:: Exception
0x1850038, task 0x10325d8
Thu Jan 20 22:33:31 : FATAL ERROR: System
segmentation/access violation
caught.
Class: qqos_SystemException
Error #: [101, 321]
Detected at: qqos_MainExFilter at 1
Error Time: Thu Jan 20 22:33:31
Exception occurred (locally) on partition
"xxxx_cl0_Part4",
(partitionId =
DD8782F0-CB74-11D3-91A1-8088AF65AA77:0x34e:0x1,
taskId =
[DD8782F0-CB74-11D3-91A1-8088AF65AA77:0x3
4e.26]) in application
"xxxx_cl0", pid 1163 on node MCPORCA1 in
environment mcfem01.
Thu Jan 20 22:33:31 :
Thu Jan 20 22:33:31 : THROW:: Exception
0x1850188, task 0x10325d8
Thu Jan 20 22:33:31 : SYSTEM ERROR: Error during
Serialization.
Class: qqsp_SerializationException
Error #: [201, 34]
Detected at: qqlo_Xlate at 1
Error Time: Thu Jan 20 22:33:31
Exception occurred (locally) on partition
"xxxx_cl0_Part4",
(partitionId =
DD8782F0-CB74-11D3-91A1-8088AF65AA77:0x34e:0x1,
taskId =
[DD8782F0-CB74-11D3-91A1-8088AF65AA77:0x3
4e.26]) in application
"xxxx_cl0", pid 1163 on node MCPORCA1 in
environment mcfem01.
Thu Jan 20 22:33:31 :
Thu Jan 20 22:33:31 : THROW:: Exception
0x1850188, task 0x10325d8
Thu Jan 20 22:33:31 : SYSTEM ERROR: Error
serializing attribute 1 of
class mach_status
(serialization type 6).
Class: qqsp_SerializationException
Error #: [1001, 267]
Detected at: qqrt_4GLClassType::InstanceXlate
at 1
Error Time: Thu Jan 20 22:33:31
Exception occurred (locally) on partition
"xxxx_cl0_Part4",
(partitionId =
DD8782F0-CB74-11D3-91A1-8088AF65AA77:0x34e:0x1,
taskId =
[DD8782F0-CB74-11D3-91A1-8088AF65AA77:0x3
4e.26]) in application
"xxxx_cl0", pid 1163 on node MCPORCA1 in
environment mcfem01.
Thu Jan 20 22:33:31 :
Thu Jan 20 22:33:31 : THROW:: Exception
0x1850038, task 0x10325d8
Thu Jan 20 22:33:31 : FATAL ERROR: System
segmentation/access violation
caught.
Class: qqos_SystemException
Thanks.
Ravi Kallamadi
For the archives, go to:
http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To
unsubscribe, send in a new
email the word: 'Unsubscribe' to:
forte-users-requestlists.xpedior.comSerialization errors can also come from mismatched id's in plans. This
happens when you have 2+ repositories containing the same code but having
different id's inside the plans. Applications built from these multiple
repositories will not be able to communicate with each other. Serialization
errors will occur when they attempt to. To fix this. Make sure that you
export all code with the "ids" flags. Check your fscript manual for more
information on this, but basically it is something like
exportworkspace <path>/<filename> ids
Overwriting a plan in Forte even with the overwrite command will not
overwrite the id's. So it might be necessary to junk a repository and start
it from scratch, importing the id's into it. This will ensure that all of
your "shared" code in the multiple repositories are in synch. And yes, this
is a huge pain.
Scott Francis
-----Original Message-----
From: Peter Sham [mailto:peter_shamyahoo.com]
Sent: Friday, January 28, 2000 10:18 AM
To: BOURDON Patrice; 'Ravindra Kallamadi'; kamranaminyahoo.com
Cc: William.K.Bhattapmusa.com
Subject: RE: (forte-users) SerializationException
Hi,
One more suggestion. You can run fscript and issue command "showapp" under
partition workshop, then you will see all the projects being pulled in for a
partition. This would show you whether your code for that attribute is
missing from the list of projects.
Regards,
Peter Sham.
BOURDON Patrice <patrice.bourdonalliance-sante.fr> wrote:
hi,
is the type of "attribute 1 of class mach_status" known of your partition ?
you can get this kind of error if you pass an object whose some type of
attribute are unknown in called partition
(but only from calling partition).
Patrice
-----Message d'origine-----
De: Ravindra Kallamadi [mailto:rkallamadiyahoo.com]
Date: jeudi 27 janvier 2000 00:12
À: kamranaminyahoo.com
Cc: William.K.Bhattapmusa.com
Objet: (forte-users) SerializationException
Has anyone experienced the following SerializationException?
Thu Jan 20 22:33:31 : End of Stack Backtrace
Thu Jan 20 22:33:31 : THROW:: Exception 0x1850038, task 0x10325d8
Thu Jan 20 22:33:31 : FATAL ERROR: System segmentation/access violation
caught.
Class: qqos_SystemException
Error #: [101, 321]
Detected at: qqos_MainExFilter at 1
Error Time: Thu Jan 20 22:33:31
Exception occurred (locally) on partition "xxxx_cl0_Part4",
(partitionId = DD8782F0-CB74-11D3-91A1-8088AF65AA77:0x34e:0x1,
taskId =
[DD8782F0-CB74-11D3-91A1-8088AF65AA77:0x34e.26]) in application
"xxxx_cl0", pid 1163 on node MCPORCA1 in environment mcfem01.
Thu Jan 20 22:33:31 :
Thu Jan 20 22:33:31 : THROW:: Exception 0x1850188, task 0x10325d8
Thu Jan 20 22:33:31 : SYSTEM ERROR: Error during Serialization.
Class: qqsp_SerializationException
Error #: [201, 34]
Detected at: qqlo_Xlate at 1
Error Time: Thu Jan 20 22:33:31
Exception occurred (locally) on partition "xxxx_cl0_Part4",
(partitionId = DD8782F0-CB74-11D3-91A1-8088AF65AA77:0x34e:0x1,
taskId =
[DD8782F0-CB74-11D3-91A1-8088AF65AA77:0x34e.26]) in application
"xxxx_cl0", pid 1163 on node MCPORCA1 in environment mcfem01.
Thu Jan 20 22:33:31 :
Thu Jan 20 22:33:31 : THROW:: Exception 0x1850188, task 0x10325d8
Thu Jan 20 22:33:31 : SYSTEM ERROR: Error serializing attribute 1 of
class mach_status
(serialization type 6).
Class: qqsp_SerializationException
Error #: [1001, 267]
Detected at: qqrt_4GLClassType::InstanceXlate at 1
Error Time: Thu Jan 20 22:33:31
Exception occurred (locally) on partition "xxxx_cl0_Part4",
(partitionId = DD8782F0-CB74-11D3-91A1-8088AF65AA77:0x34e:0x1,
taskId =
[DD8782F0-CB74-11D3-91A1-8088AF65AA77:0x34e.26]) in application
"xxxx_cl0", pid 1163 on node MCPORCA1 in environment mcfem01.
Thu Jan 20 22:33:31 :
Thu Jan 20 22:33:31 : THROW:: Exception 0x1850038, task 0x10325d8
Thu Jan 20 22:33:31 : FATAL ERROR: System segmentation/access violation
caught.
Class: qqos_SystemException
Thanks.
Ravi Kallamadi
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com
--0-1804289383-949072683=:11145
Content-Type: text/html; charset=us-ascii
<P>Hi,</P>
<P>One more suggestion. You can run fscript and issue command
"showapp" under partition workshop, then you will see all the projects being
pulled in for a partition. This would show you whether your code for
that attribute is missing from the list of projects.</P>
<P>Regards,</P>
<P>Peter Sham.</P>
<P><B><I>BOURDON Patrice <patrice.bourdonalliance-sante.fr></B></I>
wrote:<BR>
<BLOCKQUOTE style="BORDER-LEFT: #1010ff 2px solid; MARGIN-LEFT: 5px;
PADDING-LEFT: 5px">hi,<BR><BR>is the type of "attribute 1 of class
mach_status" known of your partition ?<BR>you can get this kind of error if
you pass an object whose some type of<BR>attribute are unknown in called
partition<BR>(but only from calling
partition).<BR><BR>Patrice<BR><BR>-----Message d'origine-----<BR>De:
Ravindra Kallamadi [mailto:rkallamadiyahoo.com]<BR>Date: jeudi 27 janvier
2000 00:12<BR>À:: kamranaminyahoo.com<BR>Cc:
William.K.Bhattapmusa.com<BR>Objet: (forte-users)
SerializationException<BR><BR><BR>Has anyone experienced the following
SerializationException?<BR><BR>---------------------------------------------
-------------------------<BR>Thu Jan 20 22:33:31 : End of Stack
Backtrace<BR><BR>Thu Jan 20 22:33:31 : THROW:: Exception 0x1850038, task
0x10325d8<BR>Thu Jan 20 22:33:31 : FATAL ERROR: System segmentation/access
violation<BR>caught.<BR>Class: qqos_SystemException<BR>Error #: [101,!
321]<BR>Detected at: qqos_MainExFilter at 1<BR>Error Time: Thu Jan 20
22:33:31 <BR>Exception occurred (locally) on partition
"xxxx_cl0_Part4",<BR>(partitionId =
DD8782F0-CB74-11D3-91A1-8088AF65AA77:0x34e:0x1,<BR>taskId
=<BR>[DD8782F0-CB74-11D3-91A1-8088AF65AA77:0x34e.26]) in
application<BR>"xxxx_cl0", pid 1163 on node MCPORCA1 in environment
mcfem01.<BR>Thu Jan 20 22:33:31 : <BR>Thu Jan 20 22:33:31 : THROW::
Exception 0x1850188, task 0x10325d8<BR>Thu Jan 20 22:33:31 : SYSTEM ERROR:
Error during Serialization.<BR>Class: qqsp_SerializationException<BR>Error
#: [201, 34]<BR>Detected at: qqlo_Xlate at 1<BR>Error Time: Thu Jan 20
22:33:31 <BR>Exception occurred (locally) on partition
"xxxx_cl0_Part4",<BR>(partitionId =
DD8782F0-CB74-11D3-91A1-8088AF65AA77:0x34e:0x1,<BR>taskId
=<BR>[DD8782F0-CB74-11D3-91A1-8088AF65AA77:0x34e.26]) in
application<BR>"xxxx_cl0", pid 1163 on node MCPORCA1 in environment
mcfem01.<BR>Thu Jan 20 22:33:31 : <BR>Thu Jan 20 22:33:31 : THROW::
Exception 0x185!
0188, task 0x10325d8<BR>Thu Jan 20 22:33:31 : SYSTEM ERROR: Error
serializing attribute 1 of<BR>class mach_status<BR>(serialization type
6).<BR>Class: qqsp_SerializationException<BR>Error #: [1001,
267]<BR>Detected at: qqrt_4GLClassType::InstanceXlate at 1<BR>Error Time:
Thu Jan 20 22:33:31 <BR>Exception occurred (locally) on partition
"xxxx_cl0_Part4",<BR>(partitionId =
DD8782F0-CB74-11D3-91A1-8088AF65AA77:0x34e:0x1,<BR>taskId
=<BR>[DD8782F0-CB74-11D3-91A1-8088AF65AA77:0x34e.26]) in
application<BR>"xxxx_cl0", pid 1163 on node MCPORCA1 in environment
mcfem01.<BR>Thu Jan 20 22:33:31 : <BR>Thu Jan 20 22:33:31 : THROW::
Exception 0x1850038, task 0x10325d8<BR>Thu Jan 20 22:33:31 : FATAL ERROR:
System segmentation/access violation<BR>caught.<BR>Class:
qqos_SystemException<BR>----------------------------------------------------
-------------------<BR><BR>Thanks.<BR><BR>Ravi Kallamadi<BR><BR>--<BR>For
the archives, go to: http://lists.xpedior.com/forte-users and use<BR>the
login: fort!
e and the password: archive. To unsubscribe, send in a new <BR>email the
word: 'Unsubscribe' to:
forte-users-requestlists.xpedior.com<BR><BR>--<BR>For the archives, go to:
http://lists.xpedior.com/forte-users and use<BR>the login: forte and the
password: archive. To unsubscribe, send in a new <BR>email the word:
'Unsubscribe' to: forte-users-requestlists.xpedior.com<BR><BR></BLOCKQUOTE> -
RE: (forte-users) Segmentaion Access Violation
You are not alone, I've the same problem and I don't know how to manage.
Has anybody outhere any idea about how to avoid this misfunctioning.
Yours Daniel,
-----Mensaje original-----
De: Ravindra Kallamadi <[email protected]>
Para: [email protected] <[email protected]>
CC: [email protected] <[email protected]>
Fecha: miércoles 22 de diciembre de 1999 22:30
Asunto: (forte-users) Segmentaion Access Violation
We have been experiencing SEGV problem while running a compiled app.
We changed the app. from compiled to interpreted. I wanted to know
the recommended trace flags to capture detailed explanation for SEGV
exception?
Thanks.
Ravi Kallamadi
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]Everytime we receive a SegV inside of a compiled
partition, we flip it to interpretive code. Then we
always get the "trying to access an attribute on a Nil
object" error. In this case, a SegV makes sense when
trying to access an attribute on a nil object in
compiled "C" code.
Mark Musgrove
Senior Systems Engineer
Object Technologies, Inc
(540) 977-3861 (home)
(540) 977-2794 (fax) -
RE: (forte-users) 3J= 3M new to me error
Hi Thomas,
Thanks for your email but I think it will be interesting for Brenda not me.
It is exactly what I have expected from Forte Support: detailed information
about bugs and workarounds. But what I cannot understand is that #53398 was
released without any information about possible reasons for this problem or
suggested workarounds. My first reaction after reading this bugreport was to
open a new case at CallCenter to get more information about it. Please
release more information with your bug reports !
Regards
Zenon Adamek
Information Services
Senior Programmer Analyst
Tel: 905 712-1084 ext. 3628
Fax: 905 712-6709
E-mail: zadamekpurolator.com
-----Original Message-----
From: Thomas Degen - Sun Germany Forte Tools - Bonn
[SMTP:thomas.degensun.com]
Sent: Wednesday, September 27, 2000 9:49 AM
To: Adamek, Zenon
Cc: 'Brenda Cumming'; Forte-userslists.xpedior.com
Subject: RE: (forte-users) 3J=>3M new to me error
Hi Zenon,
bug #53398 is not a bug which will likely get fixed, it's an informational
bugreport.
You might see an errorstack like Brenda has reported (and described in
informational
bugreport #53398) probably when you are doing something illegal that is
possible
via Forte Tool but Forte is not trapping it for performance reasons. Hence
you will see
the error coming from your illegal operation only at runtime, probably
only
while
running interpreted in the Forte IDE, but in worst case it might be even a
segmentation
violation.
Technotes 12448 'Sudden client partition crashes at runtime' and 11225
'Don't reparent
mapped Widgets between UserWindows at runtime' explain this matter . See
attached.
But maybe Brenda is much more experiencing a problem as described by Forte
Technote 11398 'Read Only Workspace Errors using ListViews or ActiveX
control'
that might get easily resolved via setting of FORTE_YIELD_THROTTLE=0.
Good Luck and Best Regards !
BTW: I've logged bug #53398, so I've felt responsible to explain its real
background.
Thomas
Thomas Degen
Sun Microsystems - Forte Tools
Forte CTE & Sustaining Group
Technical Support Germany
tel.:+49.228/91499-50
MailTo:thomas.degensun.com
Technote 11398 Read Only Workspace Errors using ListViews or ActiveX
control
SCENARIO:
Getting some unusual interpreter errors that result in an error stating
that
the workspace has been set to read only. Please see Enclosures for the
two
most common error stacks that have been encountered. The abbreviated
versions of the errors are:
- Can't read record (record size = -1)
- Id in index does not match id in record header in data file
- Recursive deserialization attempted.
- Unknown Mark type in deserialization
- Could not read record (64,74615) from repository data file.
Header
is corrupt.
These errors can be happening in either the development environment when
running from one of the development workshops, or with the deployed
application.
The bug outlined in this Technote may be the culprit if the errors above
are
seen when running a client on Windows NT or Motif and the user interface
incorporates ActiveX controls or ListView/TreeView widgets.
CAUSE:
Basically what is happening is that in rare circumstances Forte may invoke
a
nested copy of the interpreter while the first interpreter has yielded.
This
is not a problem in and of itself, but in the case where the original
interpreter was in the middle of a repository fetch when it yielded, and
the second interpreter needs to fetch code as well, we will get one of the
errors listed above, depending on the exact timing. The reason for the
errors is that the repository code at this level is thread-safe but not
re-entrant. It is protected by a mutex that is already owned by the
current task. Which, given the scenario outlined here, where the two
interpreters are running inside of the same task, results in the nested
interpreter being allowed to change data out from under the first.
While for every fetch one or more calls to WindowSystem.Yield will be made
(this is there to prevent the semblance of system lock-up on Win 3.1,
where
Yield is the only way other applications can be allowed to run), there is
a parameter which controls how often to actually yield, which by default
is
set to one out of every 100 calls. This is the reason the problem is
intermittent--you need a yield to occur during a repository fetch
which starts another interpreter which also needs to fetch code from
disk.
The reason this has only surfaced recently is that the nested interpreter
scenario can only happen in 2 cases that we know of:
- ActiveX controls which respond to events/Windows messages
- Outline fields/ListViews with column(s) mapped to virtual
attributes
In all other normal cases, the yield can process the message (typically a
paint message) without starting another interpreter, so regardless of
whether
the first interpreter yielded during a repository operation or not, there
is
no conflict.
SOLUTION:
The workaround is to prevent yields altogether by setting the
FORTE_YIELD_THROTTLE environment variable equal to 0 in the client's
environment. This should have no detrimental effects since the yield code
is in place solely for Windows 3.1x clients.
ERROR STACK 1
SYSTEM ERROR: Because of a prior error, your workspace was set to
read-only to
prevent the application from attempting to write to the repository. The
repository and work you have saved to the repository are safe. If your
workspace
contains unsaved work, you may use the following procedure to save this
work.
First, export the changed components. Then, shut down and restart this
application and reopen this workspace in read-write mode. Finally, import
the
changed components and save your workspace.
Class: qqrp_RepResourceException
Error #: [1101, 695]
Detected at: qqrp_Session::GetObjectById
Last TOOL statement: method EFWindowController.EFEventLoop
Error Time: Tue Nov 18 15:58:47
Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
(partitionId = 7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1,
taskId =
[7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1.23]) in application
"ConPlus_GUI_cl0", pid 147 on node ISD060 in environment EdgeTest.
The remainder of the Error Manager stack is:
SYSTEM ERROR: Internal Error attempting to deserialize element (64,67470)
(fetch
bitmask is 0x20). Your workspace is now read-only to prevent the
application
from attempting to write to the repository. The repository and work you
have
saved to the repository are safe. If your workspace contains unsaved work,
you
may use the following procedure to save this work. First, export the
changed
components. Then, shut down and restart this application and reopen this
workspace in read-write mode. Finally, import the changed components and
save
your workspace.
Class: qqrp_RepResourceException
Error #: [1101, 61]
Detected at: qqrp_LogicalSession::MaterializeObject
Last TOOL statement: method EFTabManagerNew.EFNoteBookHandler
Error Time: Tue Nov 18 15:58:47
Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
(partitionId = 7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1,
taskId =
[7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1.23]) in application
"ConPlus_GUI_cl0", pid 147 on node ISD060 in environment EdgeTest.
SYSTEM ERROR: Unknown Mark type in deserialization.
Class: qqsp_ImplementationException
Error #: [1101, 34]
Detected at: qqrp_DeSerializeObject::ProcessHdr
Error Time: Tue Nov 18 15:58:47
Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
(partitionId = 7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1,
taskId =
[7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1.23]) in application
"ConPlus_GUI_cl0", pid 147 on node ISD060 in environment EdgeTest.
ERROR STACK 2
SYSTEM ERROR: A serious error has occurred in Repository
(c:\PROGRA~1\CSSPTEST\conplu0). Corrective action may be necessary.
Notify
your repository administrator.
Class: qqsp_ImplementationException
Error #: [1101, 198]
Detected at: qqrp_Repository::Fetch
Last TOOL statement: method
SalesDevelopment_NWC.DEVNotifyofTabSetCurrent
Error Time: Wed Dec 03 10:27:22
Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
(partitionId = 769D4310-6B88-11D1-84FD-65BF87C8AA77:0x121:0x1,
taskId =
[769D4310-6B88-11D1-84FD-65BF87C8AA77:0x121:0x1.22]) in application
"ConPlus_GUI_cl0", pid 172 on node ISD42 in environment Edge.
SYSTEM ERROR: Could not read record (64,74615) from repository data file.
Header is corrupt.
Class: qqsp_ImplementationException
Error #: [1106, 612]
Detected at: qqbt_BtreeAccess::FetchDataFileRecord
Error Time: Wed Dec 03 10:27:22
Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
(partitionId = 769D4310-6B88-11D1-84FD-65BF87C8AA77:0x121:0x1,
taskId =
[769D4310-6B88-11D1-84FD-65BF87C8AA77:0x121:0x1.22]) in application
"ConPlus_GUI_cl0", pid 172 on node ISD42 in environment Edge.
Technote 11225 Don't reparent mapped Widgets between UserWindows at
runtime
It is sometimes tempting to unparent a widget from one UserWindow and
reparent
it into another at runtime. However, this can cause crashes if the widget
(or
its decendants) are "mapped" to data. Here's why...
Suppose you have two UserWindows, UW1 and UW2. UW1 contains a DataField
(DF1)
which is mapped to a TextData. UW2 contains a RadioList (RL2) which is
mapped to
a scalar Integer. At compile time, every mapped attribute is internally
assigned
a "Map ID" (a small integer) which is used to tie the Widget to its
corresponding attribute. These Map IDs are used by the Widget to look up a
pointer to their data in a "Map" which is maintained by the UserWindow.
Each
UserWindow is assumed be to independent of the others, so there is nothing
wrong
with Widgets in different UserWindows being assigned the same Map IDs.
In
this
case, let's assume that DF1 and RL2 both got assigned the same Map ID of
3. No
problem so far, since each lives in a separate UserWindow with a separate
map.
Now suppose at runtime the application "detaches" or unparents DF1 from
its
UserWindow and reparents it somewhere into UW2. When it comes time for DF1
to
paint itself the Display System it must ask the Runtime System for the
value of
DF1's mapped attribute. To do that it says "give me the value of the
TextData
for DF1. You'll find it in the Map for this UserWindow (UW1), and its Map
ID is
3". When the runtime system goes to do this it expects to find a TextData
in
this "slot" of the map, but instead it picks up the integer which is
mapped to
RL2. At best this leads to bad data being returned; more likely you get a
segfault and a crash.
If DF1 was not a mapped attribute (say, a Rectangle) there would be no
problem
because there is no data mapped to a Rectangle. If instead of moving DF1
you
created a brand new DataField on the fly there would be no problem,
because the
dynamic DataField would not have any Map ID and so couldn't conflict with
any
IDs in UW2.
So how do you solve this problem? This is exactly what Nested Windows are
all
about. While you can't move DF1 into the middle of UW2, you can nest
UW1.
This
works because UW1 brings its map with it, and when you access DF1 it knows
to
look up its value in UW1's map.
UserWindows are intended to be the "unit of compilabilty" that can be
nested
inside other UserWindows. It is dangerous to "transplant" anything from
inside
one UserWindow into another at runtime.
(Note that you can't avoid this problem by cloning DF1 because the MapID
gets
copied along with it, and the clone will fail in the same way.)
Further details explained in related technote 12448 'Sudden client
partition
crashes at runtime.'
Technote 12448 Sudden client partition crashes at runtime
Scenario : You have two UserWindows, A and B. When Window A starts up, it
instantiates an instance of B and reparents some component of B into A's
window
hierarchy.
This is not allowed and almost always leads to an error at best or at
worse a
segmentation fault.
Here's why :
When you compile a UserWindow in Forte, each "mapped attribute" (whether a
form
element or menu element) is assigned an internal ID which represents an
offset into
that UserWindow's table of mapped attributes. This offset is only valid
in the
context of the UserWindow in which it was compiled. If you detach a
FieldWidget or
MenuWidget from one compiled Window ("tmpMenu" for example) and then
parent
into another compiled window ("tmpWindow") the internal ID comes with it.
When Forte tries to make use of that copied widget it uses the ID as an
offset
into tmpWindow's table of mapped attributes. But that copied offset is
meaningless in the context of tmpWindow's table, so you get some kind off
error.
In this case it found that the data type of the variable in the slot
wasn't
what
was expected. But you might even index off the end of the table and get a
segmentation fault.
There is nothing to prevent you from dynamically creating menu items and
adding
them to a window at runtime; that will work fine. Although of course you
can't
access them via mapped attributes, since those can only be created at
compile time.
But you are not allowed to reparent a widget from one compiled UserWindow
into
the hierarchy of another.
More information may be found in technote 11225 'Don't reparent mapped
Widgets
between UserWindows at runtime'.
Possible errorstacks seen at runtime instead of a complete crash or
segmentation
violation while you are illegally reparenting a widget or menuitem between
windows
at runtime:
Map::SetSubjectData: Invalid conversion from map type 0 to subject type 22
SYSTEM ERROR: Bad parameter at location 3 in method
qqrt_MapClassAccess::ProcessSubjectData.
Class: qqsp_Exception
Error #: [1001, 381]
Detected at: qqrt_MapClassAccess::ProcessSubjectData at 3
Error Time: Wed Aug 09 13:03:57
Exception occurred (locally) on partition "testproject_CL0_Client",
(partitionId = D4914A10-36C1-11D4-91B3-419AA33BAA77:0x208:0xd,
taskId =
[D4914A10-36C1-11D4-91B3-419AA33BAA77:0x208:0xd.68]) in application
"FTLaunch_cl0", pid 672 on node ONEWAY in environment Audi3M2Env.
At 13:14 26.09.00 -0400, Adamek, Zenon wrote:
Hi,
It is the unfixed defect 53398. Please contact Forte support.
Zenon
-----Original Message-----
From: Brenda Cumming [SMTP:brenda_cummingtranscanada.com]
Sent: Tuesday, September 26, 2000 1:15 PM
To: Forte User group
Subject: (forte-users) 3J=>3M new to me error
Hi,
We are in the process of going from 3J1 to 3.0.M.2, and I am getting
this error that I am unfamiliar with on a GUI that works fine in 3J.
It
does not happen all the time, and I have been unable to establish the
pattern that kicks it off. Has anyone seen this before?
PS- this error is not occurring in the deployed (non-compiled) app,but
when I am running locally from my workspace.
SYSTEM ERROR: Bad parameter at location 6 in method
qqrt_MapClassAccess::ProcessSubjectData.
Class: qqsp_Exception
Error #: [1001, 381]
Detected at: qqrt_MapClassAccess::ProcessSubjectData at 6
Error Time: Wed Sep 20 14:32:54
Exception occurred (locally) on partition
"ABSDevtStartUp_CL0_Client",
(partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2,
taskId =
[36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
application
"Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
SYSTEM ERROR: Can't find scope 20070 for a class.
Class: qqsp_Exception
Error #: [201, 11]
Detected at: qqlo_ClassTableLoadScope at 1
Error Time: Wed Sep 20 14:32:54
Exception occurred (locally) on partition"ABSDevtStartUp_CL0_Client",
(partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2, taskId =
[36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
application
"Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
SYSTEM ERROR: Because of a prior error, your workspace was set to
read-only to prevent the application from attempting to write to the repository.
The repository and work you have saved to the repository are safe. If
your
workspace contains unsaved work, you may use the following procedure
to save this work. First, export the changed components. Then, shut down and
restart this application and reopen this workspace in read-write mode.
Finally, import the changed components and save your workspace.
Class: qqrp_RepResourceException
Error #: [1101, 695]
Detected at: qqrp_Session::IsDistributed
Last TOOL statement: method PPMeasWin.
Error Time: Wed Sep 20 14:32:54
Exception occurred (locally) on partition
"ABSDevtStartUp_CL0_Client",
(partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2, taskId =
[36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
application
"Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
SYSTEM ERROR: Internal Error attempting to deserialize element
(64,120684) (fetch bitmask is 0x20). Your workspace is now read-onlyto
prevent
the application from attempting to write to the repository. The
repository
and work you have saved to the repository are safe. If your workspace
contains unsaved work, you may use the following procedure to savethis
work.
First, export the changed components. Then, shut down and restart this
application and reopen this workspace in read-write mode. Finally, import the
changed components and save your workspace.
Class: qqrp_RepResourceException
Error #: [1101, 61]
Detected at: qqrp_LogicalSession::MaterializeObject
Error Time: Wed Sep 20 14:32:54
Exception occurred (locally) on partition
"ABSDevtStartUp_CL0_Client",
(partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2, taskId =
[36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
application
"Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
SYSTEM ERROR: Recursive Deserialization attempted, Internal Error!
Class: qqsp_UsageException with ReasonCode: SP_ER_INVALIDSTATE
Error #: [301, 231]
Detected at: qqsp_DeSerializeDriver::Run at 1
Error Time: Wed Sep 20 14:32:54
Exception occurred (locally) on partition"ABSDevtStartUp_CL0_Client",
(partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2, taskId =
[36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
application
"Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in anew
email the word: 'Unsubscribe' to:forte-users-requestlists.xpedior.com
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.comHi Thomas,
Thanks for your email but I think it will be interesting for Brenda not me.
It is exactly what I have expected from Forte Support: detailed information
about bugs and workarounds. But what I cannot understand is that #53398 was
released without any information about possible reasons for this problem or
suggested workarounds. My first reaction after reading this bugreport was to
open a new case at CallCenter to get more information about it. Please
release more information with your bug reports !
Regards
Zenon Adamek
Information Services
Senior Programmer Analyst
Tel: 905 712-1084 ext. 3628
Fax: 905 712-6709
E-mail: zadamekpurolator.com
-----Original Message-----
From: Thomas Degen - Sun Germany Forte Tools - Bonn
[SMTP:thomas.degensun.com]
Sent: Wednesday, September 27, 2000 9:49 AM
To: Adamek, Zenon
Cc: 'Brenda Cumming'; Forte-userslists.xpedior.com
Subject: RE: (forte-users) 3J=>3M new to me error
Hi Zenon,
bug #53398 is not a bug which will likely get fixed, it's an informational
bugreport.
You might see an errorstack like Brenda has reported (and described in
informational
bugreport #53398) probably when you are doing something illegal that is
possible
via Forte Tool but Forte is not trapping it for performance reasons. Hence
you will see
the error coming from your illegal operation only at runtime, probably
only
while
running interpreted in the Forte IDE, but in worst case it might be even a
segmentation
violation.
Technotes 12448 'Sudden client partition crashes at runtime' and 11225
'Don't reparent
mapped Widgets between UserWindows at runtime' explain this matter . See
attached.
But maybe Brenda is much more experiencing a problem as described by Forte
Technote 11398 'Read Only Workspace Errors using ListViews or ActiveX
control'
that might get easily resolved via setting of FORTE_YIELD_THROTTLE=0.
Good Luck and Best Regards !
BTW: I've logged bug #53398, so I've felt responsible to explain its real
background.
Thomas
Thomas Degen
Sun Microsystems - Forte Tools
Forte CTE & Sustaining Group
Technical Support Germany
tel.:+49.228/91499-50
MailTo:thomas.degensun.com
Technote 11398 Read Only Workspace Errors using ListViews or ActiveX
control
SCENARIO:
Getting some unusual interpreter errors that result in an error stating
that
the workspace has been set to read only. Please see Enclosures for the
two
most common error stacks that have been encountered. The abbreviated
versions of the errors are:
- Can't read record (record size = -1)
- Id in index does not match id in record header in data file
- Recursive deserialization attempted.
- Unknown Mark type in deserialization
- Could not read record (64,74615) from repository data file.
Header
is corrupt.
These errors can be happening in either the development environment when
running from one of the development workshops, or with the deployed
application.
The bug outlined in this Technote may be the culprit if the errors above
are
seen when running a client on Windows NT or Motif and the user interface
incorporates ActiveX controls or ListView/TreeView widgets.
CAUSE:
Basically what is happening is that in rare circumstances Forte may invoke
a
nested copy of the interpreter while the first interpreter has yielded.
This
is not a problem in and of itself, but in the case where the original
interpreter was in the middle of a repository fetch when it yielded, and
the second interpreter needs to fetch code as well, we will get one of the
errors listed above, depending on the exact timing. The reason for the
errors is that the repository code at this level is thread-safe but not
re-entrant. It is protected by a mutex that is already owned by the
current task. Which, given the scenario outlined here, where the two
interpreters are running inside of the same task, results in the nested
interpreter being allowed to change data out from under the first.
While for every fetch one or more calls to WindowSystem.Yield will be made
(this is there to prevent the semblance of system lock-up on Win 3.1,
where
Yield is the only way other applications can be allowed to run), there is
a parameter which controls how often to actually yield, which by default
is
set to one out of every 100 calls. This is the reason the problem is
intermittent--you need a yield to occur during a repository fetch
which starts another interpreter which also needs to fetch code from
disk.
The reason this has only surfaced recently is that the nested interpreter
scenario can only happen in 2 cases that we know of:
- ActiveX controls which respond to events/Windows messages
- Outline fields/ListViews with column(s) mapped to virtual
attributes
In all other normal cases, the yield can process the message (typically a
paint message) without starting another interpreter, so regardless of
whether
the first interpreter yielded during a repository operation or not, there
is
no conflict.
SOLUTION:
The workaround is to prevent yields altogether by setting the
FORTE_YIELD_THROTTLE environment variable equal to 0 in the client's
environment. This should have no detrimental effects since the yield code
is in place solely for Windows 3.1x clients.
ERROR STACK 1
SYSTEM ERROR: Because of a prior error, your workspace was set to
read-only to
prevent the application from attempting to write to the repository. The
repository and work you have saved to the repository are safe. If your
workspace
contains unsaved work, you may use the following procedure to save this
work.
First, export the changed components. Then, shut down and restart this
application and reopen this workspace in read-write mode. Finally, import
the
changed components and save your workspace.
Class: qqrp_RepResourceException
Error #: [1101, 695]
Detected at: qqrp_Session::GetObjectById
Last TOOL statement: method EFWindowController.EFEventLoop
Error Time: Tue Nov 18 15:58:47
Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
(partitionId = 7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1,
taskId =
[7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1.23]) in application
"ConPlus_GUI_cl0", pid 147 on node ISD060 in environment EdgeTest.
The remainder of the Error Manager stack is:
SYSTEM ERROR: Internal Error attempting to deserialize element (64,67470)
(fetch
bitmask is 0x20). Your workspace is now read-only to prevent the
application
from attempting to write to the repository. The repository and work you
have
saved to the repository are safe. If your workspace contains unsaved work,
you
may use the following procedure to save this work. First, export the
changed
components. Then, shut down and restart this application and reopen this
workspace in read-write mode. Finally, import the changed components and
save
your workspace.
Class: qqrp_RepResourceException
Error #: [1101, 61]
Detected at: qqrp_LogicalSession::MaterializeObject
Last TOOL statement: method EFTabManagerNew.EFNoteBookHandler
Error Time: Tue Nov 18 15:58:47
Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
(partitionId = 7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1,
taskId =
[7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1.23]) in application
"ConPlus_GUI_cl0", pid 147 on node ISD060 in environment EdgeTest.
SYSTEM ERROR: Unknown Mark type in deserialization.
Class: qqsp_ImplementationException
Error #: [1101, 34]
Detected at: qqrp_DeSerializeObject::ProcessHdr
Error Time: Tue Nov 18 15:58:47
Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
(partitionId = 7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1,
taskId =
[7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1.23]) in application
"ConPlus_GUI_cl0", pid 147 on node ISD060 in environment EdgeTest.
ERROR STACK 2
SYSTEM ERROR: A serious error has occurred in Repository
(c:\PROGRA~1\CSSPTEST\conplu0). Corrective action may be necessary.
Notify
your repository administrator.
Class: qqsp_ImplementationException
Error #: [1101, 198]
Detected at: qqrp_Repository::Fetch
Last TOOL statement: method
SalesDevelopment_NWC.DEVNotifyofTabSetCurrent
Error Time: Wed Dec 03 10:27:22
Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
(partitionId = 769D4310-6B88-11D1-84FD-65BF87C8AA77:0x121:0x1,
taskId =
[769D4310-6B88-11D1-84FD-65BF87C8AA77:0x121:0x1.22]) in application
"ConPlus_GUI_cl0", pid 172 on node ISD42 in environment Edge.
SYSTEM ERROR: Could not read record (64,74615) from repository data file.
Header is corrupt.
Class: qqsp_ImplementationException
Error #: [1106, 612]
Detected at: qqbt_BtreeAccess::FetchDataFileRecord
Error Time: Wed Dec 03 10:27:22
Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
(partitionId = 769D4310-6B88-11D1-84FD-65BF87C8AA77:0x121:0x1,
taskId =
[769D4310-6B88-11D1-84FD-65BF87C8AA77:0x121:0x1.22]) in application
"ConPlus_GUI_cl0", pid 172 on node ISD42 in environment Edge.
Technote 11225 Don't reparent mapped Widgets between UserWindows at
runtime
It is sometimes tempting to unparent a widget from one UserWindow and
reparent
it into another at runtime. However, this can cause crashes if the widget
(or
its decendants) are "mapped" to data. Here's why...
Suppose you have two UserWindows, UW1 and UW2. UW1 contains a DataField
(DF1)
which is mapped to a TextData. UW2 contains a RadioList (RL2) which is
mapped to
a scalar Integer. At compile time, every mapped attribute is internally
assigned
a "Map ID" (a small integer) which is used to tie the Widget to its
corresponding attribute. These Map IDs are used by the Widget to look up a
pointer to their data in a "Map" which is maintained by the UserWindow.
Each
UserWindow is assumed be to independent of the others, so there is nothing
wrong
with Widgets in different UserWindows being assigned the same Map IDs.
In
this
case, let's assume that DF1 and RL2 both got assigned the same Map ID of
3. No
problem so far, since each lives in a separate UserWindow with a separate
map.
Now suppose at runtime the application "detaches" or unparents DF1 from
its
UserWindow and reparents it somewhere into UW2. When it comes time for DF1
to
paint itself the Display System it must ask the Runtime System for the
value of
DF1's mapped attribute. To do that it says "give me the value of the
TextData
for DF1. You'll find it in the Map for this UserWindow (UW1), and its Map
ID is
3". When the runtime system goes to do this it expects to find a TextData
in
this "slot" of the map, but instead it picks up the integer which is
mapped to
RL2. At best this leads to bad data being returned; more likely you get a
segfault and a crash.
If DF1 was not a mapped attribute (say, a Rectangle) there would be no
problem
because there is no data mapped to a Rectangle. If instead of moving DF1
you
created a brand new DataField on the fly there would be no problem,
because the
dynamic DataField would not have any Map ID and so couldn't conflict with
any
IDs in UW2.
So how do you solve this problem? This is exactly what Nested Windows are
all
about. While you can't move DF1 into the middle of UW2, you can nest
UW1.
This
works because UW1 brings its map with it, and when you access DF1 it knows
to
look up its value in UW1's map.
UserWindows are intended to be the "unit of compilabilty" that can be
nested
inside other UserWindows. It is dangerous to "transplant" anything from
inside
one UserWindow into another at runtime.
(Note that you can't avoid this problem by cloning DF1 because the MapID
gets
copied along with it, and the clone will fail in the same way.)
Further details explained in related technote 12448 'Sudden client
partition
crashes at runtime.'
Technote 12448 Sudden client partition crashes at runtime
Scenario : You have two UserWindows, A and B. When Window A starts up, it
instantiates an instance of B and reparents some component of B into A's
window
hierarchy.
This is not allowed and almost always leads to an error at best or at
worse a
segmentation fault.
Here's why :
When you compile a UserWindow in Forte, each "mapped attribute" (whether a
form
element or menu element) is assigned an internal ID which represents an
offset into
that UserWindow's table of mapped attributes. This offset is only valid
in the
context of the UserWindow in which it was compiled. If you detach a
FieldWidget or
MenuWidget from one compiled Window ("tmpMenu" for example) and then
parent
into another compiled window ("tmpWindow") the internal ID comes with it.
When Forte tries to make use of that copied widget it uses the ID as an
offset
into tmpWindow's table of mapped attributes. But that copied offset is
meaningless in the context of tmpWindow's table, so you get some kind off
error.
In this case it found that the data type of the variable in the slot
wasn't
what
was expected. But you might even index off the end of the table and get a
segmentation fault.
There is nothing to prevent you from dynamically creating menu items and
adding
them to a window at runtime; that will work fine. Although of course you
can't
access them via mapped attributes, since those can only be created at
compile time.
But you are not allowed to reparent a widget from one compiled UserWindow
into
the hierarchy of another.
More information may be found in technote 11225 'Don't reparent mapped
Widgets
between UserWindows at runtime'.
Possible errorstacks seen at runtime instead of a complete crash or
segmentation
violation while you are illegally reparenting a widget or menuitem between
windows
at runtime:
Map::SetSubjectData: Invalid conversion from map type 0 to subject type 22
SYSTEM ERROR: Bad parameter at location 3 in method
qqrt_MapClassAccess::ProcessSubjectData.
Class: qqsp_Exception
Error #: [1001, 381]
Detected at: qqrt_MapClassAccess::ProcessSubjectData at 3
Error Time: Wed Aug 09 13:03:57
Exception occurred (locally) on partition "testproject_CL0_Client",
(partitionId = D4914A10-36C1-11D4-91B3-419AA33BAA77:0x208:0xd,
taskId =
[D4914A10-36C1-11D4-91B3-419AA33BAA77:0x208:0xd.68]) in application
"FTLaunch_cl0", pid 672 on node ONEWAY in environment Audi3M2Env.
At 13:14 26.09.00 -0400, Adamek, Zenon wrote:
Hi,
It is the unfixed defect 53398. Please contact Forte support.
Zenon
-----Original Message-----
From: Brenda Cumming [SMTP:brenda_cummingtranscanada.com]
Sent: Tuesday, September 26, 2000 1:15 PM
To: Forte User group
Subject: (forte-users) 3J=>3M new to me error
Hi,
We are in the process of going from 3J1 to 3.0.M.2, and I am getting
this error that I am unfamiliar with on a GUI that works fine in 3J.
It
does not happen all the time, and I have been unable to establish the
pattern that kicks it off. Has anyone seen this before?
PS- this error is not occurring in the deployed (non-compiled) app,but
when I am running locally from my workspace.
SYSTEM ERROR: Bad parameter at location 6 in method
qqrt_MapClassAccess::ProcessSubjectData.
Class: qqsp_Exception
Error #: [1001, 381]
Detected at: qqrt_MapClassAccess::ProcessSubjectData at 6
Error Time: Wed Sep 20 14:32:54
Exception occurred (locally) on partition
"ABSDevtStartUp_CL0_Client",
(partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2,
taskId =
[36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
application
"Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
SYSTEM ERROR: Can't find scope 20070 for a class.
Class: qqsp_Exception
Error #: [201, 11]
Detected at: qqlo_ClassTableLoadScope at 1
Error Time: Wed Sep 20 14:32:54
Exception occurred (locally) on partition"ABSDevtStartUp_CL0_Client",
(partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2, taskId =
[36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
application
"Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
SYSTEM ERROR: Because of a prior error, your workspace was set to
read-only to prevent the application from attempting to write to the repository.
The repository and work you have saved to the repository are safe. If
your
workspace contains unsaved work, you may use the following procedure
to save this work. First, export the changed components. Then, shut down and
restart this application and reopen this workspace in read-write mode.
Finally, import the changed components and save your workspace.
Class: qqrp_RepResourceException
Error #: [1101, 695]
Detected at: qqrp_Session::IsDistributed
Last TOOL statement: method PPMeasWin.
Error Time: Wed Sep 20 14:32:54
Exception occurred (locally) on partition
"ABSDevtStartUp_CL0_Client",
(partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2, taskId =
[36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
application
"Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
SYSTEM ERROR: Internal Error attempting to deserialize element
(64,120684) (fetch bitmask is 0x20). Your workspace is now read-onlyto
prevent
the application from attempting to write to the repository. The
repository
and work you have saved to the repository are safe. If your workspace
contains unsaved work, you may use the following procedure to savethis
work.
First, export the changed components. Then, shut down and restart this
application and reopen this workspace in read-write mode. Finally, import the
changed components and save your workspace.
Class: qqrp_RepResourceException
Error #: [1101, 61]
Detected at: qqrp_LogicalSession::MaterializeObject
Error Time: Wed Sep 20 14:32:54
Exception occurred (locally) on partition
"ABSDevtStartUp_CL0_Client",
(partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2, taskId =
[36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
application
"Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
SYSTEM ERROR: Recursive Deserialization attempted, Internal Error!
Class: qqsp_UsageException with ReasonCode: SP_ER_INVALIDSTATE
Error #: [301, 231]
Detected at: qqsp_DeSerializeDriver::Run at 1
Error Time: Wed Sep 20 14:32:54
Exception occurred (locally) on partition"ABSDevtStartUp_CL0_Client",
(partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2, taskId =
[36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
application
"Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in anew
email the word: 'Unsubscribe' to:forte-users-requestlists.xpedior.com
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com -
RE: (forte-users) FW: (forte-users)
Hi there
Thanks very much for the solution - just wanted to let you know . We
implemented the design that technote 11378 suggested .
It worked .
Thanks very much
Cheers
Jen
-----Original Message-----
From: Adamek, Zenon [mailto:ZAdamekpurolator.com]
Sent: Tuesday, 20 March, 2001 9:21 PM
To: 'forte-userslists.xpedior.com'
Subject: (forte-users) FW: (forte-users)
Hi David,
The problem is that the SO uses an attribute of its class ACBAccount as
the ObjectReference pointer. SO is not a stateless object. The possible
scenario before crash can be that client A and B calls SO at the same
time. A's thread creates ACBAccount gets the ObjectReference. At this
point B's thread is activated, does the same as A creates new
ObjectReference. Probably the next switch between A and B will be in the
Connect() (B should wait for OLE server). If A is reactivated it doesn't
get the original own reference but the B's reference. It can cause the
crash and means that a thread can use reference created in some other
thread.
Regards,
Zenon
-----Original Message-----
From: David McPaul [SMTP:dmcpaullumley.com.au]
Sent: Monday, March 19, 2001 11:52 PM
To: 'forte-userslists.xpedior.com'
Subject: RE: (forte-users)
Jenni,
As Zenon has pointed out, technote 11378 talks about problems that
can occur if the calls made to an OLE object are not from within the same
thread the OLE object was created in. It goes on to show a design to
avoid
this.
However, the code you have given DOES communicate to the OLE object
in the same thread as it was created. So the problem as I see it is more
likely to be that the OLE object is not being garbage collected. Although
you do explicitly NIL out the ACBAccount object there is a technote 12453
that deals with the need to set the ObjectReference of CDispatch objects
to
NIL to allow the OLE object to be completely reclaimed by the garbage
collector. Failure to do so when using code that creates a new OLE object
every time you ask for an account validation will eventually run the
partition out of memory.
As pointed out in a previous post you can also increase
FORTE_STACK_SIZE but this will delay the problem not correct it.
Rather than create the connection each time you may want to think
about redesigning the method as shown in tech note 11378.
Cheers
David
-----Original Message-----
From: Adamek, Zenon [mailto:ZAdamekpurolator.com]
Sent: Tuesday, March 20, 2001 5:05 AM
To: 'Els, Jenni'
Cc: 'forte-userslists.xpedior.com'
Subject: RE: (forte-users)
Hi Jenni,
The most important issue by designing an OLE connection between a Forte
server partition and an OLE component is taking into account that an OLE
object can be referenced from the NT thread in Forte partition that it was
created in. It is the reason that you have no problems with your mini-app
in
single-threaded version.
This problem is discussed in the Technote 11378. You can find a workaround
for your problem there, too.
Regards,
Zenon
-----Original Message-----
From: Els, Jenni [SMTP:JElsnbs.co.za]
Sent: Monday, March 19, 2001 2:28 AM
To: 'forte-userslists.xpedior.com'
Subject: (forte-users)
Hi there
We have this situation
We are calling a Service Object (in the server partition) from ourclient
partition.This service object calls a method which calls a DLLregistered
on our server (VB code) . This VB code access a database on anotherserver
.(DSN set up on our server ).The database is sql server .
We are having the problem where for about 3 hours in the morning , the
system works perfectly. We then get a segmentation violation on this
partition . When we run interpreted we can see that this is an OLEinvoked
exception. The partition does not always show as offline in econsole
and
because it does not , we cannot 'online' another . We cannot take the
entire app down as everything hangs . Eventually our technical depthas
to
down the server
We set up a mini-app looping through and calling the DLL to simulate
the
problem . It worked fine. When we put another asynchronous task in the
method to call the service object , it erred quite soon. We thencreate
an
attribute of type mutex and locked using that. The mini-app worked.
However our app in development eventually hanged (without the
partition
coming though) .
The service Object is an environment visible service object in asingle
(non-replicated partition) . It has a dialog duration = session .
In the project is
ACB : ACBObject
ACBObject : CDispatch (shared = disallowed , distributed =
disallowed, transactional = disallowed, monitored = allowed)
ACBValidator : Object (shared = allowed , distributed =allowed,
transactional = disallowed, monitored = disallowed)
ACBVaidatorSO : ACBValidator
In this method we have this code to call the DLL
self.ACBAccount = new;
self.ACBAccount.CreateUsingCLSID(classID='{2EFD3084-7B05-11D3-857F-00105A4
8CEA0}');
pErrorMessage = new;
acbaccount.BankCode = pBankCode.value;
acbaccount.BranchCode = pBranchCode.value;
at : VariantI2 = new;
at.Value = pAccountType.Value;
acbaccount.AccountType = at.Value;
acbaccount.AccountNo = pAccountNo.value;
begin
acbaccount.Connect();
exception
when e : GenericException do
ex : GenericException = new;
ex.SetWithParams(severity = SP_ER_ERROR,
message = 'There was an error connecting to the database');
raise ex;
end;
begin
err : i2 = acbaccount.ValidateAccount();
if err != 0 then
pErrorMessage.SetValue(acbaccount.ErrDescriptionStr(iErrorCode= err));
acbaccount.Disconnect();
return false;
else
pErrorMessage.SetValue('The account is
valid!!');
acbaccount.Disconnect();
self.ACBAccount = NIL ;
return true;
end if;
exception
when e : GenericException do
acbaccount.Disconnect();
ex : GenericException = new;
ex.SetWithParams(severity = SP_ER_ERROR,
message = 'There was an error Validating the account');
Task.ErrorMgr.AddError(ex);
task.errormgr.ShowErrors();
raise e;
end;
exception
when e : GenericException do
acbaccount.Disconnect();
Task.ErrorMgr.ShowErrors();
raise e;
If anybody has any suggestions , they would be most welcome
Thanks very much
Cheers
Jenni Els************************************************************************Th
is e-mail is intended for the use of the individual or entity named above
and may contain information that is confidential and privileged. If you
are not the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this e-mail is strictly
prohibited. If you have received this e-mail in error, please notify us
immediately at helpdesklumley.com.au and destroy the original message.
While this mail and any attachments have been scanned for common computer
viruses and found to be virus free, we recommend you also perform your own
virus checking processes before opening any attachments.
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com--
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com
WARNING:
Any unauthorised use or interception of this email is illegal. If this email
is not intended for you, you may not copy, distribute nor disclose the
contents to anyone. Save for bona fide company matters, the BoE Group does
not accept any responsibility for the opinions expressed in this email.
For further details please see: http://www.nbs.co.za/emaildisclaim.htmHi there
Thanks very much for the solution - just wanted to let you know . We
implemented the design that technote 11378 suggested .
It worked .
Thanks very much
Cheers
Jen
-----Original Message-----
From: Adamek, Zenon [mailto:ZAdamekpurolator.com]
Sent: Tuesday, 20 March, 2001 9:21 PM
To: 'forte-userslists.xpedior.com'
Subject: (forte-users) FW: (forte-users)
Hi David,
The problem is that the SO uses an attribute of its class ACBAccount as
the ObjectReference pointer. SO is not a stateless object. The possible
scenario before crash can be that client A and B calls SO at the same
time. A's thread creates ACBAccount gets the ObjectReference. At this
point B's thread is activated, does the same as A creates new
ObjectReference. Probably the next switch between A and B will be in the
Connect() (B should wait for OLE server). If A is reactivated it doesn't
get the original own reference but the B's reference. It can cause the
crash and means that a thread can use reference created in some other
thread.
Regards,
Zenon
-----Original Message-----
From: David McPaul [SMTP:dmcpaullumley.com.au]
Sent: Monday, March 19, 2001 11:52 PM
To: 'forte-userslists.xpedior.com'
Subject: RE: (forte-users)
Jenni,
As Zenon has pointed out, technote 11378 talks about problems that
can occur if the calls made to an OLE object are not from within the same
thread the OLE object was created in. It goes on to show a design to
avoid
this.
However, the code you have given DOES communicate to the OLE object
in the same thread as it was created. So the problem as I see it is more
likely to be that the OLE object is not being garbage collected. Although
you do explicitly NIL out the ACBAccount object there is a technote 12453
that deals with the need to set the ObjectReference of CDispatch objects
to
NIL to allow the OLE object to be completely reclaimed by the garbage
collector. Failure to do so when using code that creates a new OLE object
every time you ask for an account validation will eventually run the
partition out of memory.
As pointed out in a previous post you can also increase
FORTE_STACK_SIZE but this will delay the problem not correct it.
Rather than create the connection each time you may want to think
about redesigning the method as shown in tech note 11378.
Cheers
David
-----Original Message-----
From: Adamek, Zenon [mailto:ZAdamekpurolator.com]
Sent: Tuesday, March 20, 2001 5:05 AM
To: 'Els, Jenni'
Cc: 'forte-userslists.xpedior.com'
Subject: RE: (forte-users)
Hi Jenni,
The most important issue by designing an OLE connection between a Forte
server partition and an OLE component is taking into account that an OLE
object can be referenced from the NT thread in Forte partition that it was
created in. It is the reason that you have no problems with your mini-app
in
single-threaded version.
This problem is discussed in the Technote 11378. You can find a workaround
for your problem there, too.
Regards,
Zenon
-----Original Message-----
From: Els, Jenni [SMTP:JElsnbs.co.za]
Sent: Monday, March 19, 2001 2:28 AM
To: 'forte-userslists.xpedior.com'
Subject: (forte-users)
Hi there
We have this situation
We are calling a Service Object (in the server partition) from ourclient
partition.This service object calls a method which calls a DLLregistered
on our server (VB code) . This VB code access a database on anotherserver
.(DSN set up on our server ).The database is sql server .
We are having the problem where for about 3 hours in the morning , the
system works perfectly. We then get a segmentation violation on this
partition . When we run interpreted we can see that this is an OLEinvoked
exception. The partition does not always show as offline in econsole
and
because it does not , we cannot 'online' another . We cannot take the
entire app down as everything hangs . Eventually our technical depthas
to
down the server
We set up a mini-app looping through and calling the DLL to simulate
the
problem . It worked fine. When we put another asynchronous task in the
method to call the service object , it erred quite soon. We thencreate
an
attribute of type mutex and locked using that. The mini-app worked.
However our app in development eventually hanged (without the
partition
coming though) .
The service Object is an environment visible service object in asingle
(non-replicated partition) . It has a dialog duration = session .
In the project is
ACB : ACBObject
ACBObject : CDispatch (shared = disallowed , distributed =
disallowed, transactional = disallowed, monitored = allowed)
ACBValidator : Object (shared = allowed , distributed =allowed,
transactional = disallowed, monitored = disallowed)
ACBVaidatorSO : ACBValidator
In this method we have this code to call the DLL
self.ACBAccount = new;
self.ACBAccount.CreateUsingCLSID(classID='{2EFD3084-7B05-11D3-857F-00105A4
8CEA0}');
pErrorMessage = new;
acbaccount.BankCode = pBankCode.value;
acbaccount.BranchCode = pBranchCode.value;
at : VariantI2 = new;
at.Value = pAccountType.Value;
acbaccount.AccountType = at.Value;
acbaccount.AccountNo = pAccountNo.value;
begin
acbaccount.Connect();
exception
when e : GenericException do
ex : GenericException = new;
ex.SetWithParams(severity = SP_ER_ERROR,
message = 'There was an error connecting to the database');
raise ex;
end;
begin
err : i2 = acbaccount.ValidateAccount();
if err != 0 then
pErrorMessage.SetValue(acbaccount.ErrDescriptionStr(iErrorCode= err));
acbaccount.Disconnect();
return false;
else
pErrorMessage.SetValue('The account is
valid!!');
acbaccount.Disconnect();
self.ACBAccount = NIL ;
return true;
end if;
exception
when e : GenericException do
acbaccount.Disconnect();
ex : GenericException = new;
ex.SetWithParams(severity = SP_ER_ERROR,
message = 'There was an error Validating the account');
Task.ErrorMgr.AddError(ex);
task.errormgr.ShowErrors();
raise e;
end;
exception
when e : GenericException do
acbaccount.Disconnect();
Task.ErrorMgr.ShowErrors();
raise e;
If anybody has any suggestions , they would be most welcome
Thanks very much
Cheers
Jenni Els************************************************************************Th
is e-mail is intended for the use of the individual or entity named above
and may contain information that is confidential and privileged. If you
are not the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this e-mail is strictly
prohibited. If you have received this e-mail in error, please notify us
immediately at helpdesklumley.com.au and destroy the original message.
While this mail and any attachments have been scanned for common computer
viruses and found to be virus free, we recommend you also perform your own
virus checking processes before opening any attachments.
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com--
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com
WARNING:
Any unauthorised use or interception of this email is illegal. If this email
is not intended for you, you may not copy, distribute nor disclose the
contents to anyone. Save for bona fide company matters, the BoE Group does
not accept any responsibility for the opinions expressed in this email.
For further details please see: http://www.nbs.co.za/emaildisclaim.htm -
Re: (forte-users) Forte and CORBA question
Hi,
The discarding the Java variable that references a distributed Forte object
doesn't cause that the distributed object will be reclaimed. In Forte client
you can use ReleaseDistReference() of the current partition (task.part) to
free the remote object. For Java client, you can implement the following
solution:
- define a method ReleaseMyObject() in the SO you are using to get the proxy
to the dist. object. As parameter for it use something that can identify
your object (attribute).
- your SO has an array or hashtable with your distributed objects, every new
object is added to it.
- in the implementation of ReleaseMyObject() find the object to release in
the array and call ReleaseDistReference() for it,
- from the Java client, call the ReleaseMyObject() for the object that is
not more needed.
Regards,
Zenon Adamek
----- Original Message -----
From: Joseph Mirwald <jomirweb.de>
To: Dave Ortman <dortmanyahoo.com>; 'Forte User Forum'
<forte-userslists.xpedior.com>
Sent: Wednesday, March 07, 2001 3:58 PM
Subject: Re: (forte-users) Forte and CORBA question
Hello Dave,
do you use a copy return or copy parameters in this method ?
If not, then maybe Forte is unable to garbage-collect this object because
it is forever
a proxy which only the server-partition may be able to drop it from memory
(object=NIL).
Try this and let us know what happens.
Hope this helps
Joseph Mirwald
At 11:49 07.03.01 -0800, Dave Ortman wrote:
We're attempting to use a Java client to access a
Forte server. In doing such, we've experienced a
problem which I hoped somebody could shed some light
on.
We've had a Java client calling Forte service objects
and passing Forte objects back and forth as CORBA
structs with no problem. However, we have experienced
some problem obtaining and using remote references to
distributed objects from the Java client.
The problem is memory utilization. Each time I obtain
a reference to a new object, the memory utilization on
the Forte server jumps up quite a bit (around 100k per
object on an NT box). Eventually, if I fetch enough
objects, the server will crash due to lack of memory.
It seems that Forte never reclaims the memory, even
though I'm not using (and don't have a handle to) this
remote objects.
The objects are very small. In fact, I created a test
Forte SO with one method, getObject(); which returns a
distributed object with a single attribute. I then
have a Java client access the getObject() method
repeatedly - discarding the reference to the object
after each iteration. After a short while, the box
will come down.
Any thoughts?
Thanks in advance,
-Dave Ortman
--- "Epari, Madhusudhan" <meparioxhp.com> wrote:
Hi All,
Following error occurs consistently on a router
partition for every call to
the service object but the partition doesn't die or
crash. I tried bumping
up the partition memory too. Any thoughts on why
it's happening?
Thanks in advance,
Madhu
SYSTEM ERROR: Failed to connect or lost connection
to the
environment manager
at FORTE_NS_ADDRESS = <Unknown>. Check that the
environment
manager is
installed at that location. If it is, then check
to be sure that
there are
enough system resources available to support this
partition.
Class: qqsp_SystemResourceException
Error #: [601, 201]
Detected at: qqdo_NsClient::FindObject at 1
Error Time: Wed Feb 21 09:30:56
Exception occurred (locally) on partition
"CSA_cl0_Part2-router",
(partitionId =
C61609A0-8270-11D3-88A9-F4D005D0AA77:0x10c5c:0x1,
taskId =
[C61609A0-8270-11D3-88A9-F4D005D0AA77:0x10c5c.8]) in
application
"MWRouting_cl1", pid 18937 on node forted1 in
environment
frtedev.
SYSTEM ERROR: Attempt to send from a partition
(C61609A0-8270-11D3-88A9-F4D005D0AA77:0x10c5c:0x1)
that no
longer exists.
Class: qqsp_DistAccessException
Error #: [601, 111]
Detected at: qqdo_PartitionMgr::SendMsg at
1
Error Time: Wed Feb 21 09:30:56
Distributed method called:
qqdo_NsServerProxy.FindObject
(object name
Unnamed) from partition
"CSA_cl0_Part2-router",
(partitionId =
C61609A0-8270-11D3-88A9-F4D005D0AA77:0x10c5c:0x1,
taskId =
[C61609A0-8270-11D3-88A9-F4D005D0AA77:0x10c5c.8]) in
application
"MWRouting_cl1", pid 18937 on node
forted1 in environment
frtedev
Exception occurred (locally) on partition
"CSA_cl0_Part2-router",
(partitionId =
C61609A0-8270-11D3-88A9-F4D005D0AA77:0x10c5c:0x1,
taskId =
[C61609A0-8270-11D3-88A9-F4D005D0AA77:0x10c5c.8])
in
application "MWRouting_cl1", pid 18937 on
node forted1 in
environment
frtedev.
LbRouter::FindMembers - CAUGHT EXCEPTION attaching
members from
For the archives, go to:
http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To
unsubscribe, send in a new
email the word: 'Unsubscribe' to:
forte-users-requestlists.xpedior.com
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com--
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.comWhy not this:
while myText.moveToString(' ') do
myText.ReplaceRange('-', myText.Offset, myText.Offset+1);
end while;
or if you prefer verbosity:
while myText.moveToString(source=' ') do
myText.ReplaceRange(source='-', startOffset=myText.Offset,
endOffset=myText.Offset+1);
end while;
-----Original Message-----
From: FatchJeBAM.com [mailto:FatchJeBAM.com]
Sent: Wednesday, January 12, 2000 2:51 PM
To: Troy.Burnsvacationclub.com; kamranaminyahoo.com
Subject: RE: (forte-users) search and replace within a TextData
How about this?? May have to play with start/end on ReplaceRange as I
didn't really test this
Anybody got a better way??
-- replace space with underscore
For x in 1 to myTextdata.LengthToEnd() do
If myTextData.IsSpace() then
MyTextdata.ReplaceRange('_'. Startoffset=myTextdata.offset,
endoffset=myTextdata.offset+1);
End if;
MyTextdata.MoveNext;
End for;
Jerry Fatcheric
-----Original Message-----
From: Burns, Troy [mailto:Troy.Burnsvacationclub.com]
Sent: Wednesday, January 12, 2000 9:40 AM
To: kamranaminyahoo.com
Subject: (forte-users) search and replace within a
TextData
Hello all,
I need to search within a textdata object, replacing all
occurrances of a
space
with another character. Can you give a quick code example
of how I would do
this?
Thanks in advance,
Troy
Troy Burns
Marriott Vacation Club Intl.
E-mail: troy.burnsvacationclub.com
Phone: (941) 688-7700 ext. 4408
For the archives, go to: http://lists.sageit.com/forte-users
and use
the login: forte and the password: archive. To unsubscribe,
send in a new
email the word: 'Unsubscribe' to:
forte-users-requestlists.sageit.com
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.sageit.com -
Re: System segmentattion access violation
There is a special utility you must run which will clean the environment
repository. It is located under the following directory:
%{FORTE_ROOT}/install/diag/bin/
It is called envedit
The command works like this:
%FORTE_ROOT%/install/diag/bin/envedit -fs -fr
%FORTE_ROOT%/sysdata/envrepos/<envrepos_name>
You can use the -i option to specifiy a script to run. Such a script will
need to look like this:
# envedit script for cleaning the environment repositories
setworkspace SystemMgr
open
browse
compactrepos
quit
quit
This will clean and compact your environment repository. Make sure that yo
ur environment is offline before you attempt this.
Mark Musgrove
Object Technologies. Inc.
<Graphic image not retained>
ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\ on 06/29/99 03:58:06 PM
To: Mark Musgrove/BCS/BBS/BLS@BLS
cc: ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\@yahoo.com@omgw,
forte-users@O1=Internet/DD.RFC-822=forte-users\@sageit.com@omgw
Subject: System segmentattion access violation
Received: from carnac.bst.bellsouth.com (bos17943.al.bst.bls.com [90.110.28
.65])
by om1.al.bst.bls.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id OAA1038
9
for <[email protected]>; Tue, 29 Jun 1999 14:56:37 -0
500 (CDT)
Received: from web502.yahoomail.com ([128.11.68.69])
by carnac.bst.bellsouth.com (Netscape Messaging Server 3.52)
with SMTP id AAA3C12 for <[email protected]>;
Tue, 29 Jun 1999 14:56:03 -0500
Received: from [206.49.176.243] by web502.yahoomail.com; Tue, 29 Jun 1999 1
2:58:06 PDT
Message-ID: <[email protected]>
Date: Tue, 29 Jun 1999 12:58:06 -0700 (PDT)
From: Jorge Espinoza <[email protected]>
Subject: System segmentattion access violation
To: [email protected]
Cc: [email protected]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Mark,
We have tried # 1. It does not work.
How do I clean the environment repository?
Thanks
Jorge
--- [email protected] wrote:
This type of segmentation violation is due to an
environment manager
repository corruption. One of the three options
below will fix it(listed
from easiest solution to most difficult). If the
first two do not work,
the third one will always fix the problem.
1. Shutdown and restart the environment.
2. If #1 does not fix the problem, then your
environment repository has
become corrupted. Shutdown the environment and
clean your environment
repository. This will fix your corruption problem
about 75 % of the time.
3. If #2 does not correct your error, then the
environment is corrupted
beyond repair. You will need to delete your current
environment repository
and rebuild it. Sometimes you can rebuild it using
an export of your
current environment(bootstrap). Many times though
the current corrupted
environment will not successfully allow you to
export the environment
definition. In this case, you will have to rebuild
your environment from
scratch.
Hope this helps...
Mark Musgrove
Object Technologies, Inc
<Graphic image not retained>
ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\ on
06/26/99 12:05:55 AM
To:
forte-users@O1=Internet/DD.RFC-822=forte-users\@SageIT.com@omgw
cc:
ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\@yahoo.com@omgw
Subject: System segmentattion access violation
Received: from carnac.bst.bellsouth.com
(bos17943.al.bst.bls.com [90.110.28
.65])
by om1.al.bst.bls.com (8.8.6
(PHNE_17135)/8.8.6) with ESMTP id XAA0132
8
for <[email protected]>; Fri,
25 Jun 1999 23:45:53 -0
500 (CDT)
Received: from pebble.SageIT.com ([206.169.110.3])
by carnac.bst.bellsouth.com (Netscape
Messaging Server 3.52)
with SMTP id AAA64AA for
<[email protected]>;
Fri, 25 Jun 1999 23:45:20 -0500
Received: (from sync@localhost) by pebble.SageIT.com
(8.6.10/8.6.9) id UAA1
3783 for forte-users-outgoing; Fri, 25 Jun 1999
20:51:51 -0700
Received: (from uucp@localhost) by pebble.SageIT.com
(8.6.10/8.6.9) id UAA1
3767 for <[email protected]>; Fri, 25 Jun 1999
20:51:46 -0700
Received: from web501.yahoomail.com(128.11.68.68) by
pebble.sagesoln.com vi
a smap (V2.0)
id xma013762; Fri, 25 Jun 99 20:51:31 -0700
Message-ID:
<[email protected]>
Received: from [206.49.176.243] by
web501.yahoomail.com; Fri, 25 Jun 1999 2
1:05:55 PDT
Date: Fri, 25 Jun 1999 21:05:55 -0700 (PDT)
From: Jorge Espinoza <[email protected]>
Subject: System segmentattion access violation
To: [email protected]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: [email protected]
Precedence: bulk
Reply-To: Jorge Espinoza <[email protected]>
Hello :
We're try connect with our Central Server Node and
have a problem, if we're make the connection with
Escript this is
succesfull, but if we're connected again with
Econsole , Launcher
Distributed or Forte Distributed then this
connection display the
following error
NLM Startup is Complete - Partition's Locale is 'c'
Loading partition FTLaunch_cl0_Client built on
03-Sep-1998 00:37:56.
There is no manager active for node FORTE1.
Type Service Flags Level
err sh * 255
cfg sp 8 255
cfg em 2 2
FTLaunch_cl0: Configuring node agent.
FTLaunch_cl0: Opening configuration repository
bt:c:\forte\sysdata\envrepos\fort
e1.
FTLaunch_cl0: Attached to manager for node FORTE1.
Type Service Flags Level
err sh * 255
cfg em 2 2
Begin Stack Backtrace
==========================================================
Trace caused by a segmentation or access violation
in the Forte
executable:
ftexec Version 3.0.J.1
Windows NT
Forte Application Environment (tm), Forte Runtime
Environment (tm),
Forte Conductor (tm):
Copyright (c) 1994-1998, Forte Software, Inc. and
its licensors.
US Patent No. 5,457,797
Forte Express (tm), Forte WebEnterprise (tm):
Copyright (c) 1995-1998, Forte Software, Inc.
All Rights Reserved.
Unpublished rights reserved under the copyright laws
of the United
States.
Wed Sep 2 22:53:49 1998
Fault at 25-Jun-1999 13:23:56, pid '180', node
'FORTE1':
User Name: Administrador
Machine Name: FORTE1 with 1 CPU(s)
OS version 4.0
Loading symbols for ...
c:\forte\install\bin\QQRP.dll
c:\forte\install\bin\QQCT.dll
c:\forte\install\bin\QQSH.dll
c:\forte\install\bin\QQKN.dll
c:\forte\install\bin\QQSM.dll
c:\forte\install\bin\ftexec.exe
c:\forte\install\bin\QQDO.dll
c:\forte\install\bin\QQCM.dll
c:\forte\install\bin\QQFO.dll
c:\forte\install\bin\QQDS.dll
c:\forte\install\bin\qqtlnt.dll
c:\forte\install\bin\w3tpwss.dll
c:\forte\install\bin\qqem.dll
c:\forte\install\bin\QQDD.dll
c:\forte\install\bin\QQRT.dll
C:\WINNT\System32\WINSPOOL.DRV
C:\WINNT\System32\rpcltc1.dll
C:\WINNT\System32\rnr20.dll
C:\WINNT\System32\rasadhlp.dll
C:\WINNT\System32\IMM32.dll
C:\WINNT\System32\spool\DRIVERS\W32X86\2\RASDDUI.DLL
C:\WINNT\system32\msafd.dll
C:\WINNT\System32\wshtcpip.dll
C:\WINNT\System32\WS2HELP.dll
C:\WINNT\System32\WS2_32.dll
C:\WINNT\System32\WSOCK32.dll
C:\WINNT\system32\ole32.dll
C:\WINNT\system32\COMCTL32.dll
C:\WINNT\system32\SHELL32.dll
C:\WINNT\system32\comdlg32.dll
C:\WINNT\system32\ADVAPI32.dll
C:\WINNT\system32\RPCRT4.dll
C:\WINNT\system32\USER32.dll
C:\WINNT\system32\GDI32.dll
C:\WINNT\system32\KERNEL32.dll
C:\WINNT\System32\ntdll.dll
C:\WINNT\system32\MSVCRT.dll
Stack backtrace ...
qqem 026e2c5d (0130bac0,00000001,00000000,013b8aa0)
QQSM 003b238a (0130bac0,013b8aa0,013f0001,013f4768)
QQKN 0024d5f1 (0130bac0,013b8aa0,013f0001,013f4748)
QQKN 00250915 (0130bac0,013b8aa0,013f4730,013f4748)
QQDO 00432d96 (0130bac0,0209fd40,000000d0,013365b8)
=== message truncated ===
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>There is a special utility you must run which will clean the environment
repository. It is located under the following directory:
%{FORTE_ROOT}/install/diag/bin/
It is called envedit
The command works like this:
%FORTE_ROOT%/install/diag/bin/envedit -fs -fr
%FORTE_ROOT%/sysdata/envrepos/<envrepos_name>
You can use the -i option to specifiy a script to run. Such a script will
need to look like this:
# envedit script for cleaning the environment repositories
setworkspace SystemMgr
open
browse
compactrepos
quit
quit
This will clean and compact your environment repository. Make sure that yo
ur environment is offline before you attempt this.
Mark Musgrove
Object Technologies. Inc.
<Graphic image not retained>
ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\ on 06/29/99 03:58:06 PM
To: Mark Musgrove/BCS/BBS/BLS@BLS
cc: ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\@yahoo.com@omgw,
forte-users@O1=Internet/DD.RFC-822=forte-users\@sageit.com@omgw
Subject: System segmentattion access violation
Received: from carnac.bst.bellsouth.com (bos17943.al.bst.bls.com [90.110.28
.65])
by om1.al.bst.bls.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id OAA1038
9
for <[email protected]>; Tue, 29 Jun 1999 14:56:37 -0
500 (CDT)
Received: from web502.yahoomail.com ([128.11.68.69])
by carnac.bst.bellsouth.com (Netscape Messaging Server 3.52)
with SMTP id AAA3C12 for <[email protected]>;
Tue, 29 Jun 1999 14:56:03 -0500
Received: from [206.49.176.243] by web502.yahoomail.com; Tue, 29 Jun 1999 1
2:58:06 PDT
Message-ID: <[email protected]>
Date: Tue, 29 Jun 1999 12:58:06 -0700 (PDT)
From: Jorge Espinoza <[email protected]>
Subject: System segmentattion access violation
To: [email protected]
Cc: [email protected]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Mark,
We have tried # 1. It does not work.
How do I clean the environment repository?
Thanks
Jorge
--- [email protected] wrote:
This type of segmentation violation is due to an
environment manager
repository corruption. One of the three options
below will fix it(listed
from easiest solution to most difficult). If the
first two do not work,
the third one will always fix the problem.
1. Shutdown and restart the environment.
2. If #1 does not fix the problem, then your
environment repository has
become corrupted. Shutdown the environment and
clean your environment
repository. This will fix your corruption problem
about 75 % of the time.
3. If #2 does not correct your error, then the
environment is corrupted
beyond repair. You will need to delete your current
environment repository
and rebuild it. Sometimes you can rebuild it using
an export of your
current environment(bootstrap). Many times though
the current corrupted
environment will not successfully allow you to
export the environment
definition. In this case, you will have to rebuild
your environment from
scratch.
Hope this helps...
Mark Musgrove
Object Technologies, Inc
<Graphic image not retained>
ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\ on
06/26/99 12:05:55 AM
To:
forte-users@O1=Internet/DD.RFC-822=forte-users\@SageIT.com@omgw
cc:
ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\@yahoo.com@omgw
Subject: System segmentattion access violation
Received: from carnac.bst.bellsouth.com
(bos17943.al.bst.bls.com [90.110.28
.65])
by om1.al.bst.bls.com (8.8.6
(PHNE_17135)/8.8.6) with ESMTP id XAA0132
8
for <[email protected]>; Fri,
25 Jun 1999 23:45:53 -0
500 (CDT)
Received: from pebble.SageIT.com ([206.169.110.3])
by carnac.bst.bellsouth.com (Netscape
Messaging Server 3.52)
with SMTP id AAA64AA for
<[email protected]>;
Fri, 25 Jun 1999 23:45:20 -0500
Received: (from sync@localhost) by pebble.SageIT.com
(8.6.10/8.6.9) id UAA1
3783 for forte-users-outgoing; Fri, 25 Jun 1999
20:51:51 -0700
Received: (from uucp@localhost) by pebble.SageIT.com
(8.6.10/8.6.9) id UAA1
3767 for <[email protected]>; Fri, 25 Jun 1999
20:51:46 -0700
Received: from web501.yahoomail.com(128.11.68.68) by
pebble.sagesoln.com vi
a smap (V2.0)
id xma013762; Fri, 25 Jun 99 20:51:31 -0700
Message-ID:
<[email protected]>
Received: from [206.49.176.243] by
web501.yahoomail.com; Fri, 25 Jun 1999 2
1:05:55 PDT
Date: Fri, 25 Jun 1999 21:05:55 -0700 (PDT)
From: Jorge Espinoza <[email protected]>
Subject: System segmentattion access violation
To: [email protected]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: [email protected]
Precedence: bulk
Reply-To: Jorge Espinoza <[email protected]>
Hello :
We're try connect with our Central Server Node and
have a problem, if we're make the connection with
Escript this is
succesfull, but if we're connected again with
Econsole , Launcher
Distributed or Forte Distributed then this
connection display the
following error
NLM Startup is Complete - Partition's Locale is 'c'
Loading partition FTLaunch_cl0_Client built on
03-Sep-1998 00:37:56.
There is no manager active for node FORTE1.
Type Service Flags Level
err sh * 255
cfg sp 8 255
cfg em 2 2
FTLaunch_cl0: Configuring node agent.
FTLaunch_cl0: Opening configuration repository
bt:c:\forte\sysdata\envrepos\fort
e1.
FTLaunch_cl0: Attached to manager for node FORTE1.
Type Service Flags Level
err sh * 255
cfg em 2 2
Begin Stack Backtrace
==========================================================
Trace caused by a segmentation or access violation
in the Forte
executable:
ftexec Version 3.0.J.1
Windows NT
Forte Application Environment (tm), Forte Runtime
Environment (tm),
Forte Conductor (tm):
Copyright (c) 1994-1998, Forte Software, Inc. and
its licensors.
US Patent No. 5,457,797
Forte Express (tm), Forte WebEnterprise (tm):
Copyright (c) 1995-1998, Forte Software, Inc.
All Rights Reserved.
Unpublished rights reserved under the copyright laws
of the United
States.
Wed Sep 2 22:53:49 1998
Fault at 25-Jun-1999 13:23:56, pid '180', node
'FORTE1':
User Name: Administrador
Machine Name: FORTE1 with 1 CPU(s)
OS version 4.0
Loading symbols for ...
c:\forte\install\bin\QQRP.dll
c:\forte\install\bin\QQCT.dll
c:\forte\install\bin\QQSH.dll
c:\forte\install\bin\QQKN.dll
c:\forte\install\bin\QQSM.dll
c:\forte\install\bin\ftexec.exe
c:\forte\install\bin\QQDO.dll
c:\forte\install\bin\QQCM.dll
c:\forte\install\bin\QQFO.dll
c:\forte\install\bin\QQDS.dll
c:\forte\install\bin\qqtlnt.dll
c:\forte\install\bin\w3tpwss.dll
c:\forte\install\bin\qqem.dll
c:\forte\install\bin\QQDD.dll
c:\forte\install\bin\QQRT.dll
C:\WINNT\System32\WINSPOOL.DRV
C:\WINNT\System32\rpcltc1.dll
C:\WINNT\System32\rnr20.dll
C:\WINNT\System32\rasadhlp.dll
C:\WINNT\System32\IMM32.dll
C:\WINNT\System32\spool\DRIVERS\W32X86\2\RASDDUI.DLL
C:\WINNT\system32\msafd.dll
C:\WINNT\System32\wshtcpip.dll
C:\WINNT\System32\WS2HELP.dll
C:\WINNT\System32\WS2_32.dll
C:\WINNT\System32\WSOCK32.dll
C:\WINNT\system32\ole32.dll
C:\WINNT\system32\COMCTL32.dll
C:\WINNT\system32\SHELL32.dll
C:\WINNT\system32\comdlg32.dll
C:\WINNT\system32\ADVAPI32.dll
C:\WINNT\system32\RPCRT4.dll
C:\WINNT\system32\USER32.dll
C:\WINNT\system32\GDI32.dll
C:\WINNT\system32\KERNEL32.dll
C:\WINNT\System32\ntdll.dll
C:\WINNT\system32\MSVCRT.dll
Stack backtrace ...
qqem 026e2c5d (0130bac0,00000001,00000000,013b8aa0)
QQSM 003b238a (0130bac0,013b8aa0,013f0001,013f4768)
QQKN 0024d5f1 (0130bac0,013b8aa0,013f0001,013f4748)
QQKN 00250915 (0130bac0,013b8aa0,013f4730,013f4748)
QQDO 00432d96 (0130bac0,0209fd40,000000d0,013365b8)
=== message truncated ===
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/> -
System segmentattion access violation
Mark,
We have tried # 1. It does not work.
How do I clean the environment repository?
Thanks
Jorge
--- [email protected] wrote:
This type of segmentation violation is due to an
environment manager
repository corruption. One of the three options
below will fix it(listed
from easiest solution to most difficult). If the
first two do not work,
the third one will always fix the problem.
1. Shutdown and restart the environment.
2. If #1 does not fix the problem, then your
environment repository has
become corrupted. Shutdown the environment and
clean your environment
repository. This will fix your corruption problem
about 75 % of the time.
3. If #2 does not correct your error, then the
environment is corrupted
beyond repair. You will need to delete your current
environment repository
and rebuild it. Sometimes you can rebuild it using
an export of your
current environment(bootstrap). Many times though
the current corrupted
environment will not successfully allow you to
export the environment
definition. In this case, you will have to rebuild
your environment from
scratch.
Hope this helps...
Mark Musgrove
Object Technologies, Inc
<Graphic image not retained>
ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\ on
06/26/99 12:05:55 AM
To:
forte-users@O1=Internet/DD.RFC-822=forte-users\@SageIT.com@omgw
cc:
ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\@yahoo.com@omgw
Subject: System segmentattion access violation
Received: from carnac.bst.bellsouth.com
(bos17943.al.bst.bls.com [90.110.28
.65])
by om1.al.bst.bls.com (8.8.6
(PHNE_17135)/8.8.6) with ESMTP id XAA0132
8
for <[email protected]>; Fri,
25 Jun 1999 23:45:53 -0
500 (CDT)
Received: from pebble.SageIT.com ([206.169.110.3])
by carnac.bst.bellsouth.com (Netscape
Messaging Server 3.52)
with SMTP id AAA64AA for
<[email protected]>;
Fri, 25 Jun 1999 23:45:20 -0500
Received: (from sync@localhost) by pebble.SageIT.com
(8.6.10/8.6.9) id UAA1
3783 for forte-users-outgoing; Fri, 25 Jun 1999
20:51:51 -0700
Received: (from uucp@localhost) by pebble.SageIT.com
(8.6.10/8.6.9) id UAA1
3767 for <[email protected]>; Fri, 25 Jun 1999
20:51:46 -0700
Received: from web501.yahoomail.com(128.11.68.68) by
pebble.sagesoln.com vi
a smap (V2.0)
id xma013762; Fri, 25 Jun 99 20:51:31 -0700
Message-ID:
<[email protected]>
Received: from [206.49.176.243] by
web501.yahoomail.com; Fri, 25 Jun 1999 2
1:05:55 PDT
Date: Fri, 25 Jun 1999 21:05:55 -0700 (PDT)
From: Jorge Espinoza <[email protected]>
Subject: System segmentattion access violation
To: [email protected]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: [email protected]
Precedence: bulk
Reply-To: Jorge Espinoza <[email protected]>
Hello :
We're try connect with our Central Server Node and
have a problem, if we're make the connection with
Escript this is
succesfull, but if we're connected again with
Econsole , Launcher
Distributed or Forte Distributed then this
connection display the
following error
NLM Startup is Complete - Partition's Locale is 'c'
Loading partition FTLaunch_cl0_Client built on
03-Sep-1998 00:37:56.
There is no manager active for node FORTE1.
Type Service Flags Level
err sh * 255
cfg sp 8 255
cfg em 2 2
FTLaunch_cl0: Configuring node agent.
FTLaunch_cl0: Opening configuration repository
bt:c:\forte\sysdata\envrepos\fort
e1.
FTLaunch_cl0: Attached to manager for node FORTE1.
Type Service Flags Level
err sh * 255
cfg em 2 2
Begin Stack Backtrace
==========================================================
Trace caused by a segmentation or access violation
in the Forte
executable:
ftexec Version 3.0.J.1
Windows NT
Forte Application Environment (tm), Forte Runtime
Environment (tm),
Forte Conductor (tm):
Copyright (c) 1994-1998, Forte Software, Inc. and
its licensors.
US Patent No. 5,457,797
Forte Express (tm), Forte WebEnterprise (tm):
Copyright (c) 1995-1998, Forte Software, Inc.
All Rights Reserved.
Unpublished rights reserved under the copyright laws
of the United
States.
Wed Sep 2 22:53:49 1998
Fault at 25-Jun-1999 13:23:56, pid '180', node
'FORTE1':
User Name: Administrador
Machine Name: FORTE1 with 1 CPU(s)
OS version 4.0
Loading symbols for ...
c:\forte\install\bin\QQRP.dll
c:\forte\install\bin\QQCT.dll
c:\forte\install\bin\QQSH.dll
c:\forte\install\bin\QQKN.dll
c:\forte\install\bin\QQSM.dll
c:\forte\install\bin\ftexec.exe
c:\forte\install\bin\QQDO.dll
c:\forte\install\bin\QQCM.dll
c:\forte\install\bin\QQFO.dll
c:\forte\install\bin\QQDS.dll
c:\forte\install\bin\qqtlnt.dll
c:\forte\install\bin\w3tpwss.dll
c:\forte\install\bin\qqem.dll
c:\forte\install\bin\QQDD.dll
c:\forte\install\bin\QQRT.dll
C:\WINNT\System32\WINSPOOL.DRV
C:\WINNT\System32\rpcltc1.dll
C:\WINNT\System32\rnr20.dll
C:\WINNT\System32\rasadhlp.dll
C:\WINNT\System32\IMM32.dll
C:\WINNT\System32\spool\DRIVERS\W32X86\2\RASDDUI.DLL
C:\WINNT\system32\msafd.dll
C:\WINNT\System32\wshtcpip.dll
C:\WINNT\System32\WS2HELP.dll
C:\WINNT\System32\WS2_32.dll
C:\WINNT\System32\WSOCK32.dll
C:\WINNT\system32\ole32.dll
C:\WINNT\system32\COMCTL32.dll
C:\WINNT\system32\SHELL32.dll
C:\WINNT\system32\comdlg32.dll
C:\WINNT\system32\ADVAPI32.dll
C:\WINNT\system32\RPCRT4.dll
C:\WINNT\system32\USER32.dll
C:\WINNT\system32\GDI32.dll
C:\WINNT\system32\KERNEL32.dll
C:\WINNT\System32\ntdll.dll
C:\WINNT\system32\MSVCRT.dll
Stack backtrace ...
qqem 026e2c5d (0130bac0,00000001,00000000,013b8aa0)
QQSM 003b238a (0130bac0,013b8aa0,013f0001,013f4768)
QQKN 0024d5f1 (0130bac0,013b8aa0,013f0001,013f4748)
QQKN 00250915 (0130bac0,013b8aa0,013f4730,013f4748)
QQDO 00432d96 (0130bac0,0209fd40,000000d0,013365b8)
=== message truncated ===
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>Mark,
We have tried # 1. It does not work.
How do I clean the environment repository?
Thanks
Jorge
--- [email protected] wrote:
This type of segmentation violation is due to an
environment manager
repository corruption. One of the three options
below will fix it(listed
from easiest solution to most difficult). If the
first two do not work,
the third one will always fix the problem.
1. Shutdown and restart the environment.
2. If #1 does not fix the problem, then your
environment repository has
become corrupted. Shutdown the environment and
clean your environment
repository. This will fix your corruption problem
about 75 % of the time.
3. If #2 does not correct your error, then the
environment is corrupted
beyond repair. You will need to delete your current
environment repository
and rebuild it. Sometimes you can rebuild it using
an export of your
current environment(bootstrap). Many times though
the current corrupted
environment will not successfully allow you to
export the environment
definition. In this case, you will have to rebuild
your environment from
scratch.
Hope this helps...
Mark Musgrove
Object Technologies, Inc
<Graphic image not retained>
ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\ on
06/26/99 12:05:55 AM
To:
forte-users@O1=Internet/DD.RFC-822=forte-users\@SageIT.com@omgw
cc:
ja.espinoza@O1=Internet/DD.RFC-822=ja_espinoza\@yahoo.com@omgw
Subject: System segmentattion access violation
Received: from carnac.bst.bellsouth.com
(bos17943.al.bst.bls.com [90.110.28
.65])
by om1.al.bst.bls.com (8.8.6
(PHNE_17135)/8.8.6) with ESMTP id XAA0132
8
for <[email protected]>; Fri,
25 Jun 1999 23:45:53 -0
500 (CDT)
Received: from pebble.SageIT.com ([206.169.110.3])
by carnac.bst.bellsouth.com (Netscape
Messaging Server 3.52)
with SMTP id AAA64AA for
<[email protected]>;
Fri, 25 Jun 1999 23:45:20 -0500
Received: (from sync@localhost) by pebble.SageIT.com
(8.6.10/8.6.9) id UAA1
3783 for forte-users-outgoing; Fri, 25 Jun 1999
20:51:51 -0700
Received: (from uucp@localhost) by pebble.SageIT.com
(8.6.10/8.6.9) id UAA1
3767 for <[email protected]>; Fri, 25 Jun 1999
20:51:46 -0700
Received: from web501.yahoomail.com(128.11.68.68) by
pebble.sagesoln.com vi
a smap (V2.0)
id xma013762; Fri, 25 Jun 99 20:51:31 -0700
Message-ID:
<[email protected]>
Received: from [206.49.176.243] by
web501.yahoomail.com; Fri, 25 Jun 1999 2
1:05:55 PDT
Date: Fri, 25 Jun 1999 21:05:55 -0700 (PDT)
From: Jorge Espinoza <[email protected]>
Subject: System segmentattion access violation
To: [email protected]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: [email protected]
Precedence: bulk
Reply-To: Jorge Espinoza <[email protected]>
Hello :
We're try connect with our Central Server Node and
have a problem, if we're make the connection with
Escript this is
succesfull, but if we're connected again with
Econsole , Launcher
Distributed or Forte Distributed then this
connection display the
following error
NLM Startup is Complete - Partition's Locale is 'c'
Loading partition FTLaunch_cl0_Client built on
03-Sep-1998 00:37:56.
There is no manager active for node FORTE1.
Type Service Flags Level
err sh * 255
cfg sp 8 255
cfg em 2 2
FTLaunch_cl0: Configuring node agent.
FTLaunch_cl0: Opening configuration repository
bt:c:\forte\sysdata\envrepos\fort
e1.
FTLaunch_cl0: Attached to manager for node FORTE1.
Type Service Flags Level
err sh * 255
cfg em 2 2
Begin Stack Backtrace
==========================================================
Trace caused by a segmentation or access violation
in the Forte
executable:
ftexec Version 3.0.J.1
Windows NT
Forte Application Environment (tm), Forte Runtime
Environment (tm),
Forte Conductor (tm):
Copyright (c) 1994-1998, Forte Software, Inc. and
its licensors.
US Patent No. 5,457,797
Forte Express (tm), Forte WebEnterprise (tm):
Copyright (c) 1995-1998, Forte Software, Inc.
All Rights Reserved.
Unpublished rights reserved under the copyright laws
of the United
States.
Wed Sep 2 22:53:49 1998
Fault at 25-Jun-1999 13:23:56, pid '180', node
'FORTE1':
User Name: Administrador
Machine Name: FORTE1 with 1 CPU(s)
OS version 4.0
Loading symbols for ...
c:\forte\install\bin\QQRP.dll
c:\forte\install\bin\QQCT.dll
c:\forte\install\bin\QQSH.dll
c:\forte\install\bin\QQKN.dll
c:\forte\install\bin\QQSM.dll
c:\forte\install\bin\ftexec.exe
c:\forte\install\bin\QQDO.dll
c:\forte\install\bin\QQCM.dll
c:\forte\install\bin\QQFO.dll
c:\forte\install\bin\QQDS.dll
c:\forte\install\bin\qqtlnt.dll
c:\forte\install\bin\w3tpwss.dll
c:\forte\install\bin\qqem.dll
c:\forte\install\bin\QQDD.dll
c:\forte\install\bin\QQRT.dll
C:\WINNT\System32\WINSPOOL.DRV
C:\WINNT\System32\rpcltc1.dll
C:\WINNT\System32\rnr20.dll
C:\WINNT\System32\rasadhlp.dll
C:\WINNT\System32\IMM32.dll
C:\WINNT\System32\spool\DRIVERS\W32X86\2\RASDDUI.DLL
C:\WINNT\system32\msafd.dll
C:\WINNT\System32\wshtcpip.dll
C:\WINNT\System32\WS2HELP.dll
C:\WINNT\System32\WS2_32.dll
C:\WINNT\System32\WSOCK32.dll
C:\WINNT\system32\ole32.dll
C:\WINNT\system32\COMCTL32.dll
C:\WINNT\system32\SHELL32.dll
C:\WINNT\system32\comdlg32.dll
C:\WINNT\system32\ADVAPI32.dll
C:\WINNT\system32\RPCRT4.dll
C:\WINNT\system32\USER32.dll
C:\WINNT\system32\GDI32.dll
C:\WINNT\system32\KERNEL32.dll
C:\WINNT\System32\ntdll.dll
C:\WINNT\system32\MSVCRT.dll
Stack backtrace ...
qqem 026e2c5d (0130bac0,00000001,00000000,013b8aa0)
QQSM 003b238a (0130bac0,013b8aa0,013f0001,013f4768)
QQKN 0024d5f1 (0130bac0,013b8aa0,013f0001,013f4748)
QQKN 00250915 (0130bac0,013b8aa0,013f4730,013f4748)
QQDO 00432d96 (0130bac0,0209fd40,000000d0,013365b8)
=== message truncated ===
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/> -
How can I repair "an access violation has occurred"
I found this message after you install the update of an audio software (Pro Tools 8.0.5) and after trying to listen to an audio recording "an access violation has occurred." In a later appeared to me the message "/ System / Library / Extensions / CDSDAAudioCaptureSupport.Kext". I removed the software completely reinstalled all audio and I havethe previous version but to no avail. I also reinstalled operating system from OS 10.6.2 Leopard up to 10.6.8 but still nothing. The message reappears when I use the audio software is not allowing me to listen to the audio (only with ProTools, while iTunes feature regularly. I do not know what to do yet.
Linc Davis wrote:
It's the PACE DRM rootkit that's installed along with the Pro Tools application. Its purpose is to cripple your computer so that you can only do what the developer chooses to let you do. If you have a problem with that, you'll have to take it up with DigiDesign, or get rid of their product.
Most absurd response to a question I have ever read...
DRM protects composers life myself from theft. I just hate it when people steal my stuff. Don't you?
I've been a PT professional user for well over a decade. My computer is in no way "crippled". I can do what I want with it and what I want with that software. I run PT with iTunes open all day long with no issue. I can import audio from my iTunes library into PT with no issue. If the audio you are trying to import is protected (from being stolen and remixed etc.) than no, you can't import it into PT. I'm pretty sure that most law abiding citizens would agree that having thier own personal livelyhood protected under law would be a good thing. But for some reason, this society thinks that musicians and other creative professionals don't deserve the same level of protection and don't need to feed thier families... -
Access violation error with 1.4.0
Our client/server application (RMI) ran fine in 1.3.1. When we compiled and deployed with 1.4.0, an error of "access violation" were thrown by Windows NT or Windown 2000 at run time. Stack trace posted as below. Anyone has any ideas on the cause of it. Thanks you very much.
Application exception occurred:
App: (pid=346)
When: 6/18/2002 @ 17:18:40.166
Exception number: c0000005 (access violation)
----> System Information <----
Computer Name: PAUL
User Name: paul
Number of Processors: 1
Processor Type: x86 Family 6 Model 4 Stepping 2
Windows Version: 4.0
Current Build: 1381
Service Pack: 6
Current Type: Uniprocessor Free
Registered Organization: Quarry Technologies
Registered Owner: Quarry Technologies
----> Task List <----
0 Idle.exe
2 System.exe
20 SMSS.exe
24 CSRSS.exe
34 winlogon.exe
40 SERVICES.exe
43 LSASS.exe
68 SPOOLSS.exe
81 defwatch.exe
86 inetd32.exe
93 MGABG.exe
94 mgasc.exe
97 mgactrl.exe
99 rtvscan.exe
45 rtsserv.exe
112 RPCSS.exe
117 portserv.exe
127 wtxregds.exe
130 WinVNC.exe
137 PSTORES.exe
140 mstask.exe
144 NOPDB.exe
200 NDDEAGNT.exe
122 explorer.exe
186 systray.exe
187 mgaqdesk.exe
44 vptray.exe
113 point32.exe
91 realplay.exe
209 winampa.exe
211 loadqm.exe
213 aim.exe
215 msmsgs.exe
218 wftpd32.exe
192 OSA.exe
238 esserver.exe
240 vpexrt.exe
241 CMD.exe
63 vncviewer.exe
255 JBuilder.exe
277 DDHELP.exe
274 CMD.exe
287 CMD.exe
293 SYSLOGD.exe
313 SYSLOGD.exe
270 P4Win.exe
310 javaw.exe
346 javaw.exe
443 javaw.exe
433 javaw.exe
354 DRWTSN32.exe
0 _Total.exe
(00400000 - 00406000)
(77f60000 - 77fbe000) dll\ntdll.dbg
(77dc0000 - 77dff000) dll\advapi32.dbg
(77f00000 - 77f5e000) dll\kernel32.dbg
(77e70000 - 77ec5000) dll\user32.dbg
(77ed0000 - 77efc000) dll\gdi32.dbg
(77e10000 - 77e67000) dll\rpcrt4.dbg
(78000000 - 78046000)
(6d330000 - 6d330000)
(77fd0000 - 77ffa000) dll\winmm.dbg
(6bd00000 - 6bd14000) K:\DDK\lib\i386\free\cm-pci.dll
(6d1d0000 - 6d1d7000)
(6d300000 - 6d30d000)
(6d210000 - 6d228000)
(6d320000 - 6d32d000)
(6d2d0000 - 6d2dd000)
(776d0000 - 776d8000) dll\wsock32.dbg
(776b0000 - 776c4000) dll\ws2_32.dbg
(776a0000 - 776a7000) dll\ws2help.dbg
(74ff0000 - 74ffe000) dll\rnr20.dbg
(77bf0000 - 77bf7000) dll\rpcltc1.dbg
(77660000 - 7766f000) dll\msafd.dbg
(77690000 - 77699000) dll\wshtcpip.dbg
(6d2f0000 - 6d2f5000)
(6d000000 - 6d0f6000)
(77c00000 - 77c18000) drv\winspool.dbg
(76ab0000 - 76ab5000) dll\imm32.dbg
(77b20000 - 77bd7000) dll\ole32.dbg
(6d180000 - 6d1d0000)
State Dump for Thread Id 0x18b
eax=6d3fb8cc ebx=00000000 ecx=00762700 edx=00000000 esi=0000012c edi=00000000
eip=77f682db esp=0006fc10 ebp=0006fc34 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:00f6e617=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
----> Stack Back Trace <----
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0006fc34 77f04f37 0000012c ffffffff 00000000 6d38b719 ntdll!NtWaitForSingleObject
0006fc7c 6d3b14c0 00000000 ffffffff 0076219c 007e0330 kernel32!WaitForSingleObject
----> Raw Stack Dump <----
0006fc10 a0 cc f1 77 2c 01 00 00 - 00 00 00 00 00 00 00 00 ...w,...........
0006fc20 50 05 7e 00 10 2f 76 00 - 30 03 7e 00 00 30 00 00 P.~../v.0.~..0..
0006fc30 04 01 00 00 7c fc 06 00 - 37 4f f0 77 2c 01 00 00 ....|...7O.w,...
0006fc40 ff ff ff ff 00 00 00 00 - 19 b7 38 6d 2c 01 00 00 ..........8m,...
0006fc50 ff ff ff ff 9c 21 76 00 - 10 2f 76 00 a0 21 76 00 .....!v../v..!v.
0006fc60 00 00 00 00 02 00 00 00 - 00 00 00 00 30 03 7e 00 ............0.~.
0006fc70 30 03 7e 00 10 2f 76 00 - 01 00 00 00 c0 fc 06 00 0.~../v.........
0006fc80 c0 14 3b 6d 00 00 00 00 - ff ff ff ff 9c 21 76 00 ..;m.........!v.
0006fc90 30 03 7e 00 30 03 7e 00 - 00 00 00 00 30 03 7e 00 0.~.0.~.....0.~.
0006fca0 d0 fc 06 00 05 86 36 6d - 5c 05 41 6d d8 fc 06 00 ......6m\.Am....
0006fcb0 00 00 00 00 00 00 00 00 - 75 85 36 6d 30 03 7e 00 ........u.6m0.~.
0006fcc0 d0 fc 06 00 b7 85 36 6d - 50 9c 77 00 30 03 7e 00 ......6mP.w.0.~.
0006fcd0 14 ff 06 00 d2 14 40 00 - bc 03 7e 00 56 00 00 00 ......@...~.V...
0006fce0 10 28 07 00 00 00 00 00 - 43 3a 5c 6a 32 73 64 6b .(......C:\j2sdk
0006fcf0 31 2e 34 2e 30 5c 6a 72 - 65 00 6a 61 76 61 77 2e 1.4.0\jre.javaw.
0006fd00 65 78 65 00 12 00 00 00 - a0 fe 06 00 00 e0 fd 7f exe.............
0006fd10 00 00 00 00 a9 a0 f6 77 - 9c fe 06 00 00 00 00 80 .......w........
0006fd20 70 fe 06 00 00 e0 fd 7f - 00 f0 fd 7f 00 00 00 00 p...............
0006fd30 5c 00 52 00 65 00 67 00 - 69 00 73 00 74 00 72 00 \.R.e.g.i.s.t.r.
0006fd40 79 00 5c 00 4d 00 61 00 - 63 00 68 00 69 00 6e 00 y.\.M.a.c.h.i.n.
State Dump for Thread Id 0x156
eax=02c29d90 ebx=007648d0 ecx=02c29d90 edx=00000009 esi=02c29d90 edi=26dbfd64
eip=6d3318d5 esp=26dbfc6c ebp=26dbfc88 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000206
function: <nosymbols>
6d3318c0 8d4df0 lea ecx,[ebp-0x10] ss:27cbe68e=????????
6d3318c3 e875000000 call 6d33193d
6d3318c8 5f pop edi
6d3318c9 5e pop esi
6d3318ca c9 leave
6d3318cb c3 ret
6d3318cc 56 push esi
6d3318cd 8bf1 mov esi,ecx
6d3318cf 8b5604 mov edx,[esi+0x4] ds:03b28796=????????
6d3318d2 83c208 add edx,0x8
FAULT ->6d3318d5 8b4210 mov eax,[edx+0x10] ds:00efea0f=????????
6d3318d8 85c0 test eax,eax
6d3318da 7f25 jg 6d331901
6d3318dc 7d1b jge 6d3318f9
6d3318de 83c9ff or ecx,0xff
6d3318e1 6a04 push 0x4
6d3318e3 2bc8 sub ecx,eax
6d3318e5 8b4608 mov eax,[esi+0x8] ds:03b28796=????????
6d3318e8 d3e0 shl eax,cl
6d3318ea 8b4a4c mov ecx,[edx+0x4c] ds:00efea0f=????????
6d3318ed 8d440807 lea eax,[eax+ecx+0x7] ds:03b28797=????????
6d3318f1 59 pop ecx
----> Stack Back Trace <----
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
26dbfc88 6d34d03a 02c29d90 02c37c48 22fc8df4 02c37c48 <nosymbols>
State Dump for Thread Id 0x160
eax=00000004 ebx=00000000 ecx=052c2748 edx=00000000 esi=00000320 edi=00000000
eip=77f682db esp=26dffc10 ebp=26dffc34 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:27cfe617=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
----> Stack Back Trace <----
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
26dffc34 77f04f37 00000320 ffffffff 00000000 6d38d2fe ntdll!NtWaitForSingleObject
26dffc7c 6d39ead0 00000000 00000000 00000001 00767d30 kernel32!WaitForSingleObject
State Dump for Thread Id 0x11a
eax=00000004 ebx=00000000 ecx=052c2a60 edx=00000000 esi=00000430 edi=00000000
eip=77f682db esp=26e3fbd4 ebp=26e3fbf8 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:27d3e5db=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
----> Stack Back Trace <----
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
26e3fbf8 77f04f37 00000430 ffffffff 00000000 6d38d2fe ntdll!NtWaitForSingleObject
26e3fc40 6d39ead0 00000000 00000000 00000001 007670b0 kernel32!WaitForSingleObject
----> Raw Stack Dump <----
26e3fbd4 a0 cc f1 77 30 04 00 00 - 00 00 00 00 00 00 00 00 ...w0...........
26e3fbe4 b0 70 76 00 4c b3 75 00 - 10 87 76 00 30 04 00 00 .pv.L.u...v.0...
26e3fbf4 2a 14 39 6d 40 fc e3 26 - 37 4f f0 77 30 04 00 00 *.9m@..&7O.w0...
26e3fc04 ff ff ff ff 00 00 00 00 - fe d2 38 6d 30 04 00 00 ..........8m0...
26e3fc14 ff ff ff ff 00 00 00 00 - 40 27 2c 05 b0 70 76 00 ........@',..pv.
26e3fc24 00 00 00 00 b0 70 76 00 - 30 04 00 00 00 00 00 00 .....pv.0.......
26e3fc34 f4 8f 76 00 02 00 00 00 - 00 00 00 00 64 fc e3 26 ..v.........d..&
26e3fc44 d0 ea 39 6d 00 00 00 00 - 00 00 00 00 01 00 00 00 ..9m............
26e3fc54 b0 70 76 00 40 27 2c 05 - b0 70 76 00 70 3c b3 22 .pv.@',..pv.p<."
26e3fc64 84 fc e3 26 aa e7 36 6d - 00 88 76 00 00 00 00 00 ...&..6m..v.....
26e3fc74 00 00 00 00 b0 70 76 00 - b0 70 76 00 ac 3c b3 22 .....pv..pv..<."
26e3fc84 b8 fc e3 26 0d 96 ab 00 - b0 70 76 00 d0 fc e3 26 ...&.....pv....&
26e3fc94 00 00 00 00 00 00 00 00 - 9c fc e3 26 00 00 00 00 ...........&....
26e3fca4 d0 fc e3 26 c8 52 b7 22 - 00 00 00 00 70 3c b3 22 ...&.R."....p<."
26e3fcb4 c8 fc e3 26 f8 fc e3 26 - 9f 2d ab 00 00 00 00 00 ...&...&.-......
26e3fcc4 51 76 ab 00 00 00 00 00 - 00 00 00 00 40 27 2c 05 Qv..........@',.
26e3fcd4 03 00 00 00 40 27 2c 05 - d4 fc e3 26 34 0a b8 22 ....@',....&4.."
26e3fce4 20 fd e3 26 78 0c b8 22 - 00 00 00 00 c8 09 b8 22 ..&x.."......."
26e3fcf4 18 fd e3 26 40 fd e3 26 - 76 2e ab 00 00 00 00 00 ...&@..&v.......
26e3fd04 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
State Dump for Thread Id 0x1ca
eax=00000000 ebx=00000000 ecx=00000001 edx=00000000 esi=26e7ff28 edi=00000000
eip=77f6791f esp=26e7ff14 ebp=26e7ff30 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000206
function: NtDelayExecution
77f67914 b827000000 mov eax,0x27
77f67919 8d542404 lea edx,[esp+0x4] ss:27d7e91b=????????
77f6791d cd2e int 2e
77f6791f c20800 ret 0x8
77f67922 8bc0 mov eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
26e7ff30 77f1cebe 0000000a 00000000 6d39138c 0000000a ntdll!NtDelayExecution
26e7ff5c 6d3af3f5 0076a380 0000000a 00000000 00000000 kernel32!Sleep
State Dump for Thread Id 0x1c8
eax=78002432 ebx=00000000 ecx=6d38ac38 edx=00000000 esi=00000120 edi=00000000
eip=77f682db esp=26ebfef4 ebp=26ebff18 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:27dbe8fb=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
26ebff18 77f04f37 00000120 ffffffff 00000000 6d38b6bf ntdll!NtWaitForSingleObject
26ebff60 6d3af53e 00000001 ffffffff 22b40f78 0076a210 kernel32!WaitForSingleObject
State Dump for Thread Id 0x15e
eax=78002432 ebx=00000000 ecx=0006fa28 edx=00000000 esi=0000069c edi=00000000
eip=77f682db esp=26effe3c ebp=26effe60 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:27dfe843=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
26effe60 77f04f37 0000069c ffffffff 00000000 6d390d49 ntdll!NtWaitForSingleObject
26effea0 6d390d8d 00000001 6d38e927 0076b370 0076b2c0 kernel32!WaitForSingleObject
State Dump for Thread Id 0x1c4
eax=00000001 ebx=00000000 ecx=26f3fc28 edx=00000000 esi=000001f4 edi=00000000
eip=77f682db esp=26f3fe80 ebp=26f3fea4 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:27e3e887=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
26f3fea4 77f04f37 000001f4 ffffffff 00000000 6d38b719 ntdll!NtWaitForSingleObject
26f3feec 6d3c1f67 00000000 ffffffff 0076b190 01e37000 kernel32!WaitForSingleObject
*----> Raw Stack Dump <----*
26f3fe80 a0 cc f1 77 f4 01 00 00 - 00 00 00 00 00 00 00 00 ...w............
26f3fe90 10 c3 76 00 50 29 76 00 - 30 b0 76 00 30 b0 76 00 ..v.P)v.0.v.0.v.
26f3fea0 e0 c3 76 00 ec fe f3 26 - 37 4f f0 77 f4 01 00 00 ..v....&7O.w....
26f3feb0 ff ff ff ff 00 00 00 00 - 19 b7 38 6d f4 01 00 00 ..........8m....
26f3fec0 ff ff ff ff 90 b1 76 00 - 90 b1 76 00 50 29 76 00 ......v...v.P)v.
26f3fed0 00 00 00 00 02 00 00 00 - cc 03 00 00 30 b0 76 00 ............0.v.
26f3fee0 30 b0 76 00 50 29 76 00 - 01 00 00 00 00 00 00 00 0.v.P)v.........
26f3fef0 67 1f 3c 6d 00 00 00 00 - ff ff ff ff 90 b1 76 00 g.<m..........v.
26f3ff00 00 70 e3 01 40 ff f3 26 - 00 00 00 00 46 29 3c 6d .p..@..&....F)<m
26f3ff10 e0 b0 76 00 30 b0 76 00 - 80 c2 76 00 30 b0 76 00 ..v.0.v...v.0.v.
26f3ff20 e0 c3 76 00 00 d8 76 00 - 08 d8 76 00 f4 db 76 00 ..v...v...v...v.
26f3ff30 54 ff f3 26 30 b0 76 00 - 30 b0 76 00 08 d8 76 00 T..&0.v.0.v...v.
26f3ff40 6c ff f3 26 02 f9 3a 6d - 30 b0 76 00 30 b0 76 00 l..&..:m0.v.0.v.
26f3ff50 30 b0 76 00 30 b0 76 00 - e0 c3 76 00 00 d8 76 00 0.v.0.v...v...v.
26f3ff60 08 d8 76 00 f4 db 76 00 - c0 c3 76 00 84 ff f3 26 ..v...v...v....&
26f3ff70 d2 f8 3a 6d 18 88 b5 02 - 30 b0 76 00 cb fe 38 6d ..:m....0.v...8m
26f3ff80 80 c2 76 00 b8 ff f3 26 - 8d 24 00 78 30 b0 76 00 ..v....&.$.x0.v.
26f3ff90 18 88 b5 02 d0 f8 06 00 - 80 c2 76 00 ff ff ff ff ..........v.....
26f3ffa0 90 ff f3 26 91 76 11 80 - dc ff f3 26 6a f5 00 78 ...&.v.....&j..x
26f3ffb0 d0 33 03 78 00 00 00 00 - ec ff f3 26 de 4e f0 77 .3.x.......&.N.w
State Dump for Thread Id 0x1ac
eax=00000004 ebx=00000000 ecx=02b73c40 edx=00000000 esi=00000500 edi=2717fbfc
eip=77f682db esp=2717fbe0 ebp=2717fc04 iopl=0 ov up ei pl nz na pe cy
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000a03
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:2807e5e7=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
2717fc04 77f04f37 00000500 000493e0 00000000 6d38d2fe ntdll!NtWaitForSingleObject
2717fc4c 6d39ead0 000493e0 00000000 00000001 0077f5e0 kernel32!WaitForSingleObject
*----> Raw Stack Dump <----*
2717fbe0 a0 cc f1 77 00 05 00 00 - 00 00 00 00 fc fb 17 27 ...w...........'
2717fbf0 e0 f5 77 00 ec b2 75 00 - f0 f4 77 00 00 a2 2f 4d ..w...u...w.../M
2717fc00 ff ff ff ff 4c fc 17 27 - 37 4f f0 77 00 05 00 00 ....L..'7O.w....
2717fc10 e0 93 04 00 00 00 00 00 - fe d2 38 6d 00 05 00 00 ..........8m....
2717fc20 e0 93 04 00 00 00 00 00 - 38 b1 32 05 e0 f5 77 00 ........8.2...w.
2717fc30 00 00 00 00 e0 f5 77 00 - 00 05 00 00 00 00 00 00 ......w.........
2717fc40 02 00 00 00 02 00 00 00 - 00 00 00 00 70 fc 17 27 ............p..'
2717fc50 d0 ea 39 6d e0 93 04 00 - 00 00 00 00 01 00 00 00 ..9m............
2717fc60 e0 f5 77 00 38 b1 32 05 - e0 f5 77 00 70 3c b3 22 ..w.8.2...w.p<."
2717fc70 90 fc 17 27 aa e7 36 6d - a0 e3 76 00 e0 93 04 00 ...'..6m..v.....
2717fc80 00 00 00 00 e0 f5 77 00 - e0 f5 77 00 ac 3c b3 22 ......w...w..<."
2717fc90 c4 fc 17 27 0d 96 ab 00 - e0 f5 77 00 dc fc 17 27 ...'......w....'
2717fca0 e0 93 04 00 00 00 00 00 - a8 fc 17 27 ac 3c b3 22 ...........'.<."
2717fcb0 dc fc 17 27 c8 52 b7 22 - 00 00 00 00 70 3c b3 22 ...'.R."....p<."
2717fcc0 d4 fc 17 27 0c fd 17 27 - 9f 2d ab 00 00 00 00 00 ...'...'.-......
2717fcd0 51 76 ab 00 e0 93 04 00 - 00 00 00 00 c0 ae 32 05 Qv............2.
2717fce0 01 00 00 00 00 00 00 00 - 01 00 00 00 c0 ae 32 05 ..............2.
2717fcf0 e0 fc 17 27 b9 c8 d6 22 - 3c fd 17 27 60 ca d6 22 ...'..."<..'`.."
2717fd00 00 00 00 00 b0 c7 d6 22 - 3c fd 17 27 5c fd 17 27 ......."<..'\..'
2717fd10 9f 2d ab 00 00 00 00 00 - 00 00 00 00 e8 a7 66 05 .-............f.
State Dump for Thread Id 0x1be
eax=02b621d8 ebx=7766b100 ecx=00000001 edx=00000000 esi=0007b2b8 edi=00000568
eip=77f682db esp=271bf6a4 ebp=271bf6f8 iopl=0 nv up ei ng nz ac pe cy
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000293
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:280be0ab=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
271bf6f8 77661202 00000568 0000052c 00000002 00000004 ntdll!NtWaitForSingleObject
271bfb60 776bb101 0000052c 271bfc00 271bfc10 00000000 msafd!<nosymbols>
271bfb98 776bb08c 0000052c 271bfc00 271bfc10 00000000 ws2_32!WSAAccept
271bfc14 00ab960d 0076fe84 271bfc58 271bfc54 271bfc28 ws2_32!accept
*----> Raw Stack Dump <----*
271bf6a4 ce 89 66 77 68 05 00 00 - 01 00 00 00 d0 f6 1b 27 ..fwh..........'
271bf6b4 d4 b2 07 00 bc b2 07 00 - 1a 00 00 00 00 44 be ab .............D..
271bf6c4 0d 17 c2 01 ff ff ff ff - ff ff ff 7f ff ff ff ff ................
271bf6d4 ff ff ff 7f 00 00 00 00 - 58 ae 07 00 ad 1f 6a 77 ........X.....jw
271bf6e4 d8 11 66 77 2c 05 00 00 - 00 00 00 00 00 00 00 00 ..fw,...........
271bf6f4 00 00 00 00 60 fb 1b 27 - 02 12 66 77 68 05 00 00 ....`..'..fwh...
271bf704 2c 05 00 00 02 00 00 00 - 04 00 00 00 00 00 00 00 ,...............
271bf714 18 69 07 00 28 88 07 00 - 66 00 02 00 00 00 00 00 .i..(...f.......
271bf724 00 00 00 00 00 00 00 00 - 08 00 00 00 00 00 00 00 ................
271bf734 00 00 00 00 00 00 00 00 - 00 00 00 00 e9 03 00 00 ................
271bf744 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271bf754 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271bf764 00 00 00 00 02 00 00 00 - 00 00 00 00 00 00 00 00 ................
271bf774 01 00 00 00 06 00 00 00 - 00 00 00 00 00 00 00 00 ................
271bf784 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271bf794 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271bf7a4 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271bf7b4 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271bf7c4 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271bf7d4 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
State Dump for Thread Id 0x1ce
eax=00ab017d ebx=7766b100 ecx=00000011 edx=00000000 esi=0007b548 edi=000005cc
eip=77f682db esp=271ff6a4 ebp=271ff6f8 iopl=0 nv up ei ng nz ac pe cy
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000293
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:280fe0ab=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
271ff6f8 77661202 000005cc 00000590 00000002 00000004 ntdll!NtWaitForSingleObject
271ffb60 776bb101 00000590 271ffc00 271ffc10 00000000 msafd!<nosymbols>
271ffb98 776bb08c 00000590 271ffc00 271ffc10 00000000 ws2_32!WSAAccept
271ffc14 00ab960d 00777e44 271ffc58 271ffc54 271ffc28 ws2_32!accept
*----> Raw Stack Dump <----*
271ff6a4 ce 89 66 77 cc 05 00 00 - 01 00 00 00 d0 f6 1f 27 ..fw...........'
271ff6b4 64 b5 07 00 4c b5 07 00 - 1a 00 00 00 f0 7a 09 b5 d...L........z..
271ff6c4 0d 17 c2 01 ff ff ff ff - ff ff ff 7f ff ff ff ff ................
271ff6d4 ff ff ff 7f 00 00 00 00 - 84 ae 07 00 ad 1f 6a 77 ..............jw
271ff6e4 d8 11 66 77 90 05 00 00 - 00 00 00 00 00 00 00 00 ..fw............
271ff6f4 00 00 00 00 60 fb 1f 27 - 02 12 66 77 cc 05 00 00 ....`..'..fw....
271ff704 90 05 00 00 02 00 00 00 - 04 00 00 00 00 00 00 00 ................
271ff714 50 aa 07 00 28 88 07 00 - 66 00 02 00 00 00 00 00 P...(...f.......
271ff724 00 00 00 00 00 00 00 00 - 08 00 00 00 00 00 00 00 ................
271ff734 00 00 00 00 00 00 00 00 - 00 00 00 00 e9 03 00 00 ................
271ff744 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271ff754 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271ff764 00 00 00 00 02 00 00 00 - 00 00 00 00 00 00 00 00 ................
271ff774 01 00 00 00 06 00 00 00 - 00 00 00 00 00 00 00 00 ................
271ff784 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271ff794 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271ff7a4 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271ff7b4 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271ff7c4 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271ff7d4 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
State Dump for Thread Id 0x1c2
eax=00ab017d ebx=00000000 ecx=00000019 edx=00000000 esi=000005b0 edi=00000000
eip=77f682db esp=2723fba0 ebp=2723fbc4 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:2813e5a7=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
2723fbc4 77f04f37 000005b0 ffffffff 00000000 6d38d2fe ntdll!NtWaitForSingleObject
2723fc0c 6d39ead0 00000000 00000000 00000001 00780730 kernel32!WaitForSingleObject
*----> Raw Stack Dump <----*
2723fba0 a0 cc f1 77 b0 05 00 00 - 00 00 00 00 00 00 00 00 ...w............
2723fbb0 30 07 78 00 2c b3 75 00 - 00 07 78 00 b0 05 00 00 0.x.,.u...x.....
2723fbc0 2a 14 39 6d 0c fc 23 27 - 37 4f f0 77 b0 05 00 00 *.9m..#'7O.w....
2723fbd0 ff ff ff ff 00 00 00 00 - fe d2 38 6d b0 05 00 00 ..........8m....
2723fbe0 ff ff ff ff 00 00 00 00 - 38 ae b5 02 30 07 78 00 ........8...0.x.
2723fbf0 00 00 00 00 30 07 78 00 - b0 05 00 00 00 00 00 00 ....0.x.........
2723fc00 2c b3 75 00 02 00 00 00 - 00 00 00 00 30 fc 23 27 ,.u.........0.#'
2723fc10 d0 ea 39 6d 00 00 00 00 - 00 00 00 00 01 00 00 00 ..9m............
2723fc20 30 07 78 00 38 ae b5 02 - 30 07 78 00 70 3c b3 22 0.x.8...0.x.p<."
2723fc30 50 fc 23 27 aa e7 36 6d - 20 14 78 00 00 00 00 00 P.#'..6m .x.....
2723fc40 00 00 00 00 30 07 78 00 - 30 07 78 00 ac 3c b3 22 ....0.x.0.x..<."
2723fc50 84 fc 23 27 0d 96 ab 00 - 30 07 78 00 9c fc 23 27 ..#'....0.x...#'
2723fc60 00 00 00 00 00 00 00 00 - 68 fc 23 27 ac 3c b3 22 ........h.#'.<."
2723fc70 9c fc 23 27 c8 52 b7 22 - 00 00 00 00 70 3c b3 22 ..#'.R."....p<."
2723fc80 94 fc 23 27 c4 fc 23 27 - 9f 2d ab 00 00 00 00 00 ..#'..#'.-......
2723fc90 51 76 ab 00 00 00 00 00 - 00 00 00 00 08 ac 32 05 Qv............2.
2723fca0 01 00 00 00 08 ac 32 05 - a0 fc 23 27 34 0a b8 22 ......2...#'4.."
2723fcb0 ec fc 23 27 78 0c b8 22 - 00 00 00 00 c8 09 b8 22 ..#'x.."......."
2723fcc0 e4 fc 23 27 0c fd 23 27 - 76 2e ab 00 00 00 00 00 ..#'..#'v.......
2723fcd0 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
State Dump for Thread Id 0x1cd
eax=00000004 ebx=00000000 ecx=22d8b980 edx=00000000 esi=000005c0 edi=2727fc48
eip=77f682db esp=2727fc2c ebp=2727fc50 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000206
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:2817e633=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
2727fc50 77f04f37 000005c0 0000ea60 00000000 6d38d2fe ntdll!NtWaitForSingleObject
2727fc98 6d39ead0 0000ea60 00000000 00000001 00781270 kernel32!WaitForSingleObject
*----> Raw Stack Dump <----*
2727fc2c a0 cc f1 77 c0 05 00 00 - 00 00 00 00 48 fc 27 27 ...w........H.''
2727fc3c 70 12 78 00 6c b3 75 00 - c0 11 78 00 00 ba 3c dc p.x.l.u...x...<.
2727fc4c ff ff ff ff 98 fc 27 27 - 37 4f f0 77 c0 05 00 00 ......''7O.w....
2727fc5c 60 ea 00 00 00 00 00 00 - fe d2 38 6d c0 05 00 00 `.........8m....
2727fc6c 60 ea 00 00 00 00 00 00 - 98 d3 32 05 70 12 78 00 `.........2.p.x.
2727fc7c 00 00 00 00 70 12 78 00 - c0 05 00 00 00 00 00 00 ....p.x.........
2727fc8c 4b 96 34 6d 02 00 00 00 - 00 00 00 00 bc fc 27 27 K.4m..........''
2727fc9c d0 ea 39 6d 60 ea 00 00 - 00 00 00 00 01 00 00 00 ..9m`...........
2727fcac 70 12 78 00 98 d3 32 05 - 70 12 78 00 70 3c b3 22 p.x...2.p.x.p<."
2727fcbc dc fc 27 27 aa e7 36 6d - 20 28 78 00 60 ea 00 00 ..''..6m (x.`...
2727fccc 00 00 00 00 70 12 78 00 - 70 12 78 00 ac 3c b3 22 ....p.x.p.x..<."
2727fcdc 10 fd 27 27 0d 96 ab 00 - 70 12 78 00 28 fd 27 27 ..''....p.x.(.''
2727fcec 60 ea 00 00 00 00 00 00 - f4 fc 27 27 00 00 00 00 `.........''....
2727fcfc 28 fd 27 27 c8 52 b7 22 - 00 00 00 00 70 3c b3 22 (.''.R."....p<."
2727fd0c 20 fd 27 27 50 fd 27 27 - 9f 2d ab 00 00 00 00 00 .''P.''.-......
2727fd1c 51 76 ab 00 60 ea 00 00 - 00 00 00 00 98 d3 32 05 Qv..`.........2.
2727fd2c 03 00 00 00 98 d3 32 05 - 2c fd 27 27 92 ea d8 22 ......2.,.''..."
2727fd3c 74 fd 27 27 28 ed d8 22 - 00 00 00 00 20 ea d8 22 t.''(..".... .."
2727fd4c 74 fd 27 27 84 fd 27 27 - 7d 01 ab 00 00 00 00 00 t.''..''}.......
2727fd5c 00 00 00 00 00 00 00 00 - 00 00 00 00 98 d3 32 05 ..............2.
State Dump for Thread Id 0x1b8
eax=00000004 ebx=00000000 ecx=2323ba90 edx=00000000 esi=00000924 edi=276cfc38
eip=77f682db esp=276cfc1c ebp=276cfc40 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000206
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:285ce623=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
----> Stack Back Trace <----
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
276cfc40 77f04f37 00000924 00007530 00000000 6d38d2fe ntdll!NtWaitForSingleObject
276cfc88 6d39ead0 00007530 00000000 00000001 007dc330 kernel32!WaitForSingleObject
State Dump for Thread Id 0x18a
eax=00000004 ebx=00000000 ecx=02bbf9a0 edx=00000000 esi=000009b0 edi=00000000
eip=77f682db esp=2770fbe0 ebp=2770fc04 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:2860e5e7=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
----> Stack Back Trace <----
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
2770fc04 77f04f37 000009b0 ffffffff 00000000 6d38d2fe ntdll!NtWaitForSingleObject
2770fc4c 6d39ead0 00000000 00000000 00000001 007dda00 kernel32!WaitForSingleObject
----> Raw Stack Dump <----
2770fbe0 a0 cc f1 77 b0 09 00 00 - 00 00 00 00 00 00 00 00 ...w............
2770fbf0 00 da 7d 00 ec b3 75 00 - 80 c1 7d 00 b0 09 00 00 ..}...u...}.....
2770fc00 2a 14 39 6d 4c fc 70 27 - 37 4f f0 77 b0 09 00 00 *.9mL.p'7O.w....
2770fc10 ff ff ff ff 00 00 00 00 - fe d2 38 6d b0 09 00 00 ..........8m....
2770fc20 ff ff ff ff 00 00 00 00 - e8 ef bb 02 00 da 7d 00 ..............}.
2770fc30 00 00 00 00 00 da 7d 00 - b0 09 00 00 00 00 00 00 ......}.........
2770fc40 ec b3 75 00 02 00 00 00 - 00 00 00 00 70 fc 70 27 ..u.........p.p'
2770fc50 d0 ea 39 6d 00 00 00 00 - 00 00 00 00 01 00 00 00 ..9m............
2770fc60 00 da 7d 00 e8 ef bb 02 - 00 da 7d 00 70 3c b3 22 ..}.......}.p<."
2770fc70 90 fc 70 27 aa e7 36 6d - 20 dc 7d 00 00 00 00 00 ..p'..6m .}.....
2770fc80I am seeing exactly the same error. I started seeing it after we started making extensive use of introspection in our code. It happens repeatably when we are load testing our software.
-
Adobe Acrobat 8 Professional Random Crash (Access Violation)
hi all. first time poster. long time reader.
i have encountered an odd access violation problem - 'ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "blah" referenced memory at "blah". The memory could not be "blah" - in 'acrobat.dll' recently with a customer who is experiencing seemingly random crashes with adobe acrobat 8 professional.
they are running the application off a citrix presnetation server 4.5 server (windows server 2003 R2 with service pack 2). each server is hosting about 8 or more users per server per day. every now and then, ie once a day, adobe acrobat crashes during use. there doesn't appear to be anything consistent in so far as the action the user is performing. they will be mid-way through marking up a document and it will just crash for one of them. all the others will continue working fine.
i have access to numerous crash dumps and nothing seems to really stand out...other than 'Acrobat_3000000!AVAcroALM_Destroy'. For example...
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
0012f96c 0343c3e1 46e4e58d 0839ce58 0012faa0 Acrobat_3000000!PDDocCreateWordFinderEx+0x59641
0012f9a0 0343c479 0000004d 00000000 46e4e5f5 Acrobat_3000000!AVAcroALM_Destroy+0x30afe
0012f9d8 0343c94a 08650e08 0000004d 0012f9fc Acrobat_3000000!AVAcroALM_Destroy+0x30b96
0012fa68 0343cea2 08650e08 0000004d 0012fab0 Acrobat_3000000!AVAcroALM_Destroy+0x31067
0012faf8 0343d0a3 08650e08 0000004d 0bbf6748 Acrobat_3000000!AVAcroALM_Destroy+0x315bf
0012fb4c 0343d8da 08650e08 00000000 46e4e7e5 Acrobat_3000000!AVAcroALM_Destroy+0x317c0
0012fbc8 03182465 08e6e808 0012fc48 00000000 Acrobat_3000000!AVAcroALM_Destroy+0x31ff7
0012fc1c 0309eeba 0bbf6748 0012fc48 00000000 Acrobat_3000000!PDPageGetFlippedMatrix+0x471d
0012fc88 030ae925 00000000 08dd9798 03098f43 Acrobat_3000000!PDDocCreateWordFinderEx+0x378ef
0012fce8 0300e9f7 0003007a 0300d5c9 000004d3 Acrobat_3000000!PDDocCreateWordFinderEx+0x4735a
0012fd04 7739b6e3 0003007a 00000113 000004d3 Acrobat_3000000!WinMain+0x24a4
0012fd30 7739b874 0300d1bf 0003007a 00000113 user32!InternalCallWinProc+0x28
0012fda8 7739ba92 00000000 0300d1bf 0003007a user32!UserCallWinProcCheckWow+0x151
0012fe10 7739bad0 0012fe54 00000000 0012fe90 user32!DispatchMessageWorker+0x327
0012fe20 0300a597 0012fe54 0012fe70 03ca2d20 user32!DispatchMessageW+0xf
0012fe90 0300aece 46e4e2e5 00d40068 03ca2d20 Acrobat_3000000+0xa597
0012fec8 0300c517 00000000 0012ff2c 00000000 Acrobat_3000000!AXWasInitViaPDFL+0x76a
0012fedc 0300c649 00000005 0040a77c 0012ff2c Acrobat_3000000!AXWasInitViaPDFL+0x1db3
0012fefc 00402d5f 03000000 00400000 001524e0 Acrobat_3000000!WinMain+0xf6
0012ff30 00403281 00400000 00000000 001524e0 Acrobat+0x2d5f
0012ffc0 77e6f23b 00000000 00000000 7ffd4000 Acrobat+0x3281
0012fff0 00000000 00403402 00000000 00000000 kernel32!BaseProcessStart+0x23
...or another...
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
0012f6e0 222cb7ad ad0d64ee 00000000 1398c0d8 Annots!PlugInMain+0xa9198
0012f830 2091b7db 0012f934 0012f9f4 56433230 Annots!PlugInMain+0x1ca425
0012f8d4 20913957 0850f3a0 0340f043 0850f3a0 AcroForm!DllUnregisterServer+0x10798b
0012f900 0340f385 00000001 51ab7765 000000df AcroForm!DllUnregisterServer+0xffb07
0012f940 034dda17 0850f3a0 00000001 51ab77d1 Acrobat_3000000!AVAcroALM_Destroy+0x3aa2
0012f9f4 034454fa 00000000 084ce5c8 ffffff84 Acrobat_3000000!AVAcroALM_Destroy+0xd2134
0012fa14 034451cb 084ce5c8 ffffff84 000000df Acrobat_3000000!AVAcroALM_Destroy+0x39c17
0012fa3c 034451f0 084ce5c8 ffffff84 000000df Acrobat_3000000!AVAcroALM_Destroy+0x398e8
0012fa5c 033e4a92 00fd0540 084ce5c8 ffffff84 Acrobat_3000000!AVAcroALM_Destroy+0x3990d
0012fadc 033e6c01 084ce5c8 00000000 00000001 Acrobat_3000000!PDDocSetXAPMetadata+0xf227f
0012fb24 033b0fbf 00000065 000000e3 00000001 Acrobat_3000000!
...continued in next post 'cause it keeps getting truncated ?!0012fbb4 030abb9e 00000065 000000e3 00000201 Acrobat_3000000!PDDocSetXAPMetadata+0xd9998
0012fbd4 030abd6f 00000201 00000001 00e30065 Acrobat_3000000!PDDocCreateWordFinderEx+0x445d3
0012fbf0 7739b6e3 000200ca 00000201 00000001 Acrobat_3000000!PDDocCreateWordFinderEx+0x447a4
0012fc1c 7739b874 030abd08 000200ca 00000201 user32!InternalCallWinProc+0x28
0012fc94 7739bfce 00000000 030abd08 000200ca user32!UserCallWinProcCheckWow+0x151
0012fcc4 773b0463 030abd08 000200ca 00000201 user32!CallWindowProcAorW+0x98
0012fce4 20b8e182 030abd08 000200ca 00000201 user32!CallWindowProcA+0x1b
0012fd04 7739b6e3 000200ca 00000201 00000001 AcroForm!DllUnregisterServer+0x37a332
0012fd30 7739b874 20b8e132 000200ca 00000201 user32!InternalCallWinProc+0x28
0012fda8 7739ba92 00000000 20b8e132 000200ca user32!UserCallWinProcCheckWow+0x151
0012fe10 7739bad0 0012fe54 00000000 0012fe90 user32!DispatchMessageWorker+0x327
0012fe20 0300a597 0012fe54 0012fe70 03ca2d20 user32!DispatchMessageW+0xf
0012fe90 0300aece 51ab70ed 00d40068 03ca2d20 Acrobat_3000000+0xa597
0012fec8 0300c517 00000000 0012ff2c 00000000 Acrobat_3000000!AXWasInitViaPDFL+0x76a
0012fedc 0300c649 00000005 0040a77c 0012ff2c Acrobat_3000000!AXWasInitViaPDFL+0x1db3
0012fefc 00402d5f 03000000 00400000 001524e0 Acrobat_3000000!WinMain+0xf6
0012ff30 00403281 00400000 00000000 001524e0 Acrobat+0x2d5f
0012ffc0 77e6f23b 00000000 00000000 7ffde000 Acrobat+0x3281
0012fff0 00000000 00403402 00000000 00000000 kernel32!BaseProcessStart+0x23
is 'AVAcroALM' to do with licensing?
other than advising them to bring citrix presentation server 4.5 up to date (HRP2) i'm at a loss what to advise. citrix often have issues with seamless published applications when spread across multiple monitors (as in this case), hence, my reason to ask them to bring their software up to date. often the funtion called will be different - often times 'Acrobat.dll!PDDocCreateWordFinderEx', other times 'Acrobat.dll!PDDocAcquirePage' and there are others.
i can post more of the mini-dump if required. any - and ALL - assitance appreciated.
thanks. -
Has anyone had any issues with Microsoft Windows XP errors referencing access violations of memory? I have had this problem since the first time I installed Boot Camp Beta, and have yet to hear a reply from any of the Geniuses. In essence, I receive random but recurring errors when opening applications in Windows XP on my Boot Camp partition. Sometimes it's when I open Internet Explorer, sometimes it's when I open Wordpad, sometimes it's another application. Additionally, I consistently receive this error when closing certain enterprise level business intelligence software. I've done research and found that this is a result of code that tries to store null values in reserved memory, but that's about it. I'd really like to know if Apple has any solutions for this issue, and if not, what that will mean for those users who have purchased - or will purchase - a MacBook with the promise of being able to run Windows XP or Vista on the Intel-based MacBooks. If this issue is pervasive and not remedied, then it makes the real prospects of using a MacBook in a business setting running Windows impossible.
Reinstalling OS X isn't going to help with Windows. There is something that is special about your Windows that is making it unstable. That something may be a driver required to run it on a Mac. Still, that driver lives on the Windows side. You might have more luck running in Parallels or VMWare as the drivers for those generic, simulated machines might be more stable.
Yes, it is technically possible for MacOS X to become corrupted. That type of corruption is almost always caused by either 1) FileVault, 2) disk cloning, 3) flaky kernel extensions. Still, it is much less common than in Windows. For example, Acrobat Reader crashes on logout on my Dell work PC. It has done this as long as I can remember on every work PC I've had at 3 companies in as many states. I have the best IT support money can buy. It is not a problem, Acrobat just crashes on logout. I just have to remember to clean up the dialog boxes so the log off can complete to avoid some corporate or gov security regulation. -
Why does labview generate Dr. Watson error "C0000005 access violation"
I am running Labview 5.1.1 in Windows 2000 Professional on a machine with the following configuration
*----> System Information <----*
Computer Name: ANDANTE
User Name: Administrator
Number of Processors: 2
Processor Type: x86 Family 6 Model 8 Stepping 3
Windows 2000 Version: 5.0
Current Build: 2195
Service Pack: 4
Current Type: Multiprocessor Free
I have all of a sudden begun to experience labview crashes. The crash occurs systematically after tens of minutes; not just a few minutes, but not more than an hour or so. I am running a vi but not actively interacting with the machine (no other applications running, not even moving the mouse around). The problem happens even when running a vi that I have run successfully for extended periods of time (overnight) only 3 months ago. I have tried it with two different vis, one that I have recently made a lot of modifications to and another that has not been touched for months (since before the crashes began), and it happens with both vis. They do much different things (communicate with different GPIB or PCI boards, write to different kinds of files in different locations, etc.), so the problem seems to be vi-independent.
When the crash occurs, I see a dialog appear with the error
labview.exe has generated errors and will be closed by windows. You will need to restart the program. An error log has been created.
The Dr. Watson error log is generated and the error is
Application exception occurred:
App: (pid=1160)
When: 4/25/2004 @ 01:57:56.640
Exception number: c0000005 (access violation)
I always get the same Dr. Watson error information -- i.e., it is very reproducible. I don't really know how to interpret the rest of the Dr. Watson log, but I include the report on the first thread, which is the one with the "FAULT" in it, at the end of this email.
Looking around on the web, it may be that a temporary virus infection could have created the problem. In the period since the machines was last successfully used, I have seen two files be infected by the W32.Welchia.B.Worm virus, the files were svchost.exe and WksPatch[1].exe. These files have been quarantined and no other infected files have been found since this error began to appear.
Any ideas? I've seen on the web that reinstalling Windows 2000 and/or upgrading to Labview 7.0 might solve the problem, but it would be nice to get some confirmation before taking the time/spending the money.
Here is the state dump for the thread with the FAULT in it, as provided by Dr. Watson:
State Dump for Thread Id 0x574
eax=00000062 ebx=00000000 ecx=00000000 edx=00000004 esi=00000000 edi=05692214
eip=00748236 esp=0012fb28 ebp=0012fb28 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: StrLen
00748230 55 push ebp
00748231 8bec mov ebp,esp
00748233 8b4d08 mov ecx,[ebp+0x8] ss:00ba9a0e=????????
FAULT ->00748236 8a11 mov dl,[ecx] ds:00000000=??
00748238 8d4101 lea eax,[ecx+0x1] ds:00a79ee6=????????
0074823b 84d2 test dl,dl
0074823d 7407 jz GetCDReg+0x6f6 (00750c46)
0074823f 8a10 mov dl,[eax] ds:00000062=??
00748241 40 inc eax
00748242 84d2 test dl,dl
00748244 75f9 jnz CfgRemove+0x44f (0074ae3f)
00748246 2bc1 sub eax,ecx
00748248 48 dec eax
00748249 5d pop ebp
0074824a c3 ret
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0012FB28 00737A74 00000000 00000000 05692214 00000400 !StrLen
0012FC40 00736A45 050753E4 05692214 0012FC6C 00736724 !SetKeyboardHandlerProc
0012FC50 00736724 05692214 0012FCB4 05692214 BDBC0000 !SetKeyboardHandlerProc
0012FC6C 00736627 05692214 0569232C 00000400 00000000 !SetKeyboardHandlerProc
0012FC98 0074B470 0012FCB4 BDBD0001 00000000 0569E8E0 !SetKeyboardHandlerProc
0012FCD0 0074ACD0 00000000 0074AC10 0569FFA4 010A2418 !CfgRemove
0012FCE8 007808D5 00000000 00000000 00000001 00000000 !CfgRemove
0012FD08 007ACEB6 00000000 00000000 77E18F95 00000000 !ChkOccurrences
0012FD9C 006033DE 00000001 00000000 77E2ADC1 007A5C80 !WMainLoop
0012FF24 007B2186 00400000 00000000 00000001 00000001 !WMain
0012FFC0 7C581AF6 005C0057 0061006C 7FFDF000 C0000005 !inp
0012FFF0 00000000 007B2030 00000000 000000C8 00000100 kernel32!OpenEventA
*----> Raw Stack Dump <----*
0012fb28 40 fc 12 00 74 7a 73 00 - 00 00 00 00 00 00 00 00 @...tzs.........
0012fb38 14 22 69 05 00 04 00 00 - 16 4d 65 74 68 6f 64 20 ."i......Method
0012fb48 4e 6f 74 20 49 6d 70 6c - 65 6d 65 6e 74 65 64 00 Not Implemented.
0012fb58 55 1f f8 77 18 25 f8 77 - 2f a8 fd 74 c4 01 00 00 U..w.%.w/..t....
0012fb68 05 a5 fd 74 d0 26 ce 01 - 00 00 06 01 10 04 00 00 ...t.&..........
0012fb78 00 00 00 00 00 00 00 00 - 2e fb 69 05 42 e9 69 05 ..........i.B.i.
0012fb88 c1 2f 7b 00 00 00 00 00 - 12 04 00 00 11 04 00 00 ./{.............
0012fb98 30 fb 69 05 12 04 12 00 - bb 35 7b 00 00 00 06 01 0.i......5{.....
0012fba8 11 04 00 00 00 00 00 00 - 00 00 00 00 2e fb 69 05 ..............i.
0012fbb8 35 34 7b 00 4c 34 7b 00 - 48 00 06 01 f8 fb 12 00 54{.L4{.H.......
0012fbc8 10 04 00 00 ec 53 07 05 - 11 04 00 00 08 fc 00 00 .....S..........
0012fbd8 ee c8 77 00 30 fb 69 05 - 11 04 00 00 00 00 00 00 ..w.0.i.........
0012fbe8 00 04 00 00 01 00 00 00 - ec 53 07 05 00 04 00 00 .........S......
0012fbf8 00 38 83 00 1c fc 12 00 - 23 ca 77 00 00 38 83 00 .8......#.w..8..
0012fc08 40 ff 69 05 01 00 00 00 - 00 00 00 00 2d 00 00 00 @.i.........-...
0012fc18 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0012fc28 00 00 00 00 00 00 00 00 - 00 00 00 00 01 00 00 00 ................
0012fc38 50 fc 12 00 1a 6a 73 00 - 50 fc 12 00 45 6a 73 00 P....js.P...Ejs.
0012fc48 e4 53 07 05 14 22 69 05 - 6c fc 12 00 24 67 73 00 .S..."i.l...$gs.
0012fc58 14 22 69 05 b4 fc 12 00 - 14 22 69 05 00 00 bc bd ."i......"i.....For questions like these, you are better off contacting NI directly. Goto www.ni.com/ask for directions. It has been my experience that Dr. Watson error logs are only useful as supplementary information. It is best for support and for the forum if you can provide a clear description on how to cause the error consistently.
Maybe you are looking for
-
I just found my old ipod touch (i think 1st generation) and would like to let my toddler use it instead of my phone. I am trying to download apps but it say I need to update to 4.3 but it won't let me update. I have the most recent itunes. any idea
-
Problem with CFCACHE and cookies
I have set a heavy usage page to cache itself <cfcache action="cache" timeout="#dateadd("h","-24",Now())#"> BUT find that when this code is added as the first line of CF code, then the page does not then pick up the user from their locally stored coo
-
like the ipod movie.
-
Calling a function at the end of event
I know that I've done this before, but I can't seem to remember tonight. I want to fire a function after a tween is finished. What am I missing? buttonArea_mc.buttonMode = true; buttonArea_mc.useHandCursor = true; buttonArea_mc.alpha = 1; var myTwee
-
Hi Expert, We are implementing objective setting and appraisal supported by portal i.e. with ESS/MSS. As per the client requirement I am posting my queries as mentioned below. 1.The client does not want to route the appraisal form for an employee du