FM2 and traps

Someone recently wrote about his suspicion that FM2 was causing traps upon
exit.  I've experienced that, too, but seldom get a trap file or process
dump to go with it.  Today one was produced.  I waited until FM2 appeared
to have finished scanning anything, clicked on the X in the upper
right-hand corner, and the program closed, but the system trapped
immediately afterward.

I've found that this often happens when I delete files with FM2, even if I
wait until disk activity has apparently stopped.

--

-- 
_________________________________________________________________________
Anthropogenic global warming:  It was always a scam.

Mike Snyder
msnyder1@...

---------------------------------------------------------------------
To unsubscribe, e-mail: fm2-user-unsubscribe@...
For additional commands, e-mail: fm2-user-help@...

Re: FM2 and traps

In <CF.0B.15128.C7DAA2F4@...>, on 02/02/12
   at 10:33 AM, msnyder1@... said:

Hi Mike,

>Someone recently wrote about his suspicion that FM2 was causing traps
>upon exit.  I've experienced that, too, but seldom get a trap file or
>process dump to go with it.

That's normal if what you got was a system trap.  You need a trap dump
partition to capture this kind of information.

>upper right-hand corner, and the program closed, but the system trapped
>immediately afterward.

Did you happen to record the trap screen.  This way we might be able to
tell you why the trap occurred.

>I've found that this often happens when I delete files with FM2, even if
>I wait until disk activity has apparently stopped.

My experience so far says it is some sort of problem with the a virtual
memory data structures.  It's not directly related to disk activty.

If you have a copy of exehdr, you can turn off the flags that enable high
memory usage.

Steven

--

-- 

Re: FM2 and traps

On 02/02/12 at 05:27 PM, "Steven Levine" <steve53@...> said:

>That's normal if what you got was a system trap.  You need a trap dump
>partition to capture this kind of information.

I have one, but I made it two gigabytes, and it usually is not big enough
to write the dump files to disk.    Strangely, it's enough for the much
more common firefox traps.

> If you have a copy of exehdr, you can turn off the flags that enable high
> memory usage.

Please provide the command for this.  I do have a copy of exehdr that
seems to have come with epdf, but don't know how to make it turn off the
flags that enable high memory usage.

--

-- 
_________________________________________________________________________
Anthropogenic global warming:  It was always a scam.

Mike Snyder
msnyder1@...

Re: FM2 and traps

** Reply to message from msnyder1@... on Thu, 02 Feb 2012
22:09:30 -0500

>On 02/02/12 at 05:27 PM, "Steven Levine" <steve53@...> said:
>
>
>>That's normal if what you got was a system trap.  You need a trap dump
>>partition to capture this kind of information.
>
>I have one, but I made it two gigabytes, and it usually is not big enough
>to write the dump files to disk.    Strangely, it's enough for the much
>more common firefox traps.

This brings up questions I've been meaning to ask: 

1) How big must the trap dump partition be? Exactly the size of the RAM? Or is
a little more needed?

2) I have 2GB of RAM. Isn't 2GB the maximum size for a FAT partition? So is it
possible to set up a trap partition if you have 2GB (or more) of RAM?

--

-- 
John Small

Re: FM2 and traps

In <30.E5.20593.5225B2F4@...>, on 02/02/12
   at 10:09 PM, msnyder1@... said:

Hi Mike,

>I have one, but I made it two gigabytes, and it usually is not big enough
>to write the dump files to disk.    Strangely, it's enough for the
>much more common firefox traps.

How does the dump fail?  Trap dumps can fail for a number of reasons.  See
the attached.  The updated partition creation section covers some recently
discovered issues.

>Please provide the command for this.  I do have a copy of exehdr that
>seems to have come with epdf, but don't know how to make it turn off the
>flags that enable high memory usage.

Use

  exehdr /?

to get help.  The commands

  exehdr /nohighmem:3 fm3.exe
  exehdr /nohighmem fm3dll.dll

will turn high memory usage.  You need to repeat the first command for
each .exe.

Steven

Re: FM2 and traps

In
<201202030642.1rThxc6B93Nl34l0@...>, on
02/03/12
   at 06:42 AM, "John Small" <jsmall@...> said:

Hi John,

>1) How big must the trap dump partition be? Exactly the size of the RAM?
>Or is a little more needed?

There's no exact number for this.  The dump file consists of a header and
the physical memory image.  For a 2GiB system, the physical memory will
always less than 2GiB.  There's PCI address space and sometimes shared
video memory.

>2) I have 2GB of RAM. Isn't 2GB the maximum size for a FAT partition? So
>is it possible to set up a trap partition if you have 2GB (or more) of
>RAM?

These days there's no reason not to make the dump partition 2GiB.  If you
have more than 2GiB of RAM you need to use the dumpfs version of os2dump

 <http://home.earthlink.net/~steve53/os2diags/dumpfs.txt>

Steven

--

-- 
----------------------------------------------------------------------
"Steven Levine" <steve53@...>  eCS/Warp/DIY etc.
www.scoug.com www.ecomstation.com

Re: FM2 and traps

Hi Mike

On Thu, 02 Feb 2012 10:33:21 -0500 msnyder1@... wrote:
>
>Someone recently wrote about his suspicion that FM2 was causing traps upon
>exit.  I've experienced that, too, but seldom get a trap file or process
>dump to go with it.  Today one was produced.  I waited until FM2 appeared
>to have finished scanning anything, clicked on the X in the upper
>right-hand corner, and the program closed, but the system trapped
>immediately afterward.
>
>I've found that this often happens when I delete files with FM2, even if I
>wait until disk activity has apparently stopped.
>

I think I found the cause for this. Try the attached fm3dll.dll and let me know if it solves the 
problem. Thanks

Gregg

---------------------------------------------------------------------
To unsubscribe, e-mail: fm2-user-unsubscribe@...
For additional commands, e-mail: fm2-user-help@...

Re: FM2 and traps

Hi  Steven

I did a much better job of trapping. I hit the close button while the initial drive scan was in 
progress. All was fine until the semaphore released then FM2 trapped in DOSCALL1.DLL and 
subsequently trapped the kernel. The initial process dump isn't of much use to me at least 
as the ring 3 stack and the gate call are missing. Nothing in the kernel (actually this was a 
system trap in DOSCALL1 also) trap seem to give any indication as to what fm3dll.dll was 
doing when this all occurred. The trap screens are below. I can upload the trap dumps to 
netlabs if you would like to look at them. Thanks

Gregg

This is the initial doscall1.dll trap

Trap screen 2 found at address #70:9c84

P1=0000000b  P2=XXXXXXXX  P3=XXXXXXXX  P4=XXXXXXXX   
EAX=00000000  EBX=0000efc0  ECX=00000007  EDX=00000020 
ESI=01460a54  EDI=21920000   
DS=0053  DSACC=f0f3  DSLIM=ffffffff   
ES=0053  ESACC=f0f3  ESLIM=ffffffff   
FS=150b  FSACC=00f2  FSLIM=00000030 
GS=0000  GSACC=****  GSLIM=******** 
CS:EIP=ffef:0000e3e1  CSACC=00df  CSLIM=0000fdf8 
SS:ESP=0a27:0144efb4  SSACC=****  SSLIM=******** 
EBP=01460a44  FLG=0000020

ASCII found at #70:9c84-12 is c0010002 (Exception Code?) 
c0010002:  Unknown error code in 3175 trap info: 

Re: FM2 and traps

In <100.a8c0050018512c4f.007@...>, on 02/03/12
   at 02:26 PM, "Gregg Young" <ygk@...> said:

Hi,

>I did a much better job of trapping. I hit the close button while the
>initial drive scan was in  progress. All was fine until the semaphore
>released then FM2 trapped in DOSCALL1.DLL and  subsequently trapped the
>kernel.

I think the doscall1 trap screen is an artifact.  The cs:eip points to a
return instruction which is typical for a thread that is expected to
return from a kernel API.

The _TKDeclareInversion + 22 trap is more interesting.  I think it implies
a timing race in the kernel.  The kernel is attempting to look at a TCB
that has been erased.  The trapping instruction is

  cmp     [eax+266h], cx

and the kernel expects the eax to point to a TCB.

>(actually this was a  system trap in DOSCALL1 also) trap seem to give any
>indication as to what fm3dll.dll was  doing when this all occurred. The
>trap screens are below. I can upload the trap dumps to  netlabs if you
>would like to look at them.

Please upload them.  The information is there, but it will take a bit of
poking to extract it.

Re: FM2 and traps

On 02/03/12 at 02:09 PM, "Gregg Young" <ygk@...> said:

>I think I found the cause for this. Try the attached fm3dll.dll and let
>me know if it solves the  problem. Thanks

Thanks.  I installed them.  Only time will tell whether they help.  I'll
let you know.  I've opened and closed it once and it hasn't crashed, but
it doesn't always trap with the old .dll.

--

-- 
_________________________________________________________________________
Anthropogenic global warming:  It was always a scam.

Mike Snyder
msnyder1@...