.EXE crash

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

.EXE crash

Bruno Buzzi Brasesco
Hi,

I have an .EXE deployed with D5.1.2 working ok.

The EXE file do not work when is deployed with D5.1.4, but in the 5.1.4
image the application seems to work fine.
(after the double click in the exe file a Windows report arise and the
execution is interrupted)
I installed and re-installed Dolphin again and again but this problem still
exist.

Does anyone have any idea ?

Regards
Bruno





---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.648 / Virus Database: 415 - Release Date: 31/03/2004


Reply | Threaded
Open this post in threaded view
|

Re: .EXE crash

Christopher J. Demers
"Bruno Buzzi Brasesco" <[hidden email]> wrote in message
news:[hidden email]...
>
> I have an .EXE deployed with D5.1.2 working ok.
>
> The EXE file do not work when is deployed with D5.1.4, but in the 5.1.4
> image the application seems to work fine.
> (after the double click in the exe file a Windows report arise and the
> execution is interrupted)
> I installed and re-installed Dolphin again and again but this problem
still
> exist.

Please post an error log (EXEName.ERRORS) if one has been generated.  Also
the exact windows error message would be useful (Pressing Ctrl-Ins while the
error dialog is open can copy the message in recent version of Windows).
Does the deployed EXE size look similar to the D5.1.2 file size?  Are there
any unusual messages during the deployment?

Chris


Reply | Threaded
Open this post in threaded view
|

Re: .EXE crash

Bill Schwab-2
In reply to this post by Bruno Buzzi Brasesco
Bruno,

> I have an .EXE deployed with D5.1.2 working ok.
>
> The EXE file do not work when is deployed with D5.1.4, but in the 5.1.4
> image the application seems to work fine.
> (after the double click in the exe file a Windows report arise and the
> execution is interrupted)
> I installed and re-installed Dolphin again and again but this problem
still
> exist.

As an aside, after you solve this, you might want to verify that you are
still using the patched DLLs.  The installers are not updated, so the
Windows Installer might undo the updates.  OTOH, Blair reported that the
repair feature would not replace them.


> Does anyone have any idea ?

Look for a crash dump in a .errors (usually named in all caps, IIRC) file in
the same directory as the exe that crashed.  I _think_ the crash dump is
enabled by default, but can't swear to it because I have installers that try
to make everything work on end user machines, and those run on my machines
too.

Crash dumps are a little verbose, but are quite useful.  The usual caveat
that something might have caused a problem that later causes an "unrelated"
crash applies.  However, most of my exe-only crashes turn out to be
stripping related - otherwise, one would hopefully see the problem in
development too.  Often, stripping problems result in a non-fatal unhandled
exception, but an error during startup, etc., can cause a crash.

Good luck!

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: .EXE crash

Bruno Buzzi Brasesco
In reply to this post by Christopher J. Demers
> Please post an error log (EXEName.ERRORS) if one has been generated.  Also
> the exact windows error message would be useful (Pressing Ctrl-Ins while
the
> error dialog is open can copy the message in recent version of Windows).
> Does the deployed EXE size look similar to the D5.1.2 file size?  Are
there
> any unusual messages during the deployment?

No EXEName.errors has been generated.
OLD_EXE size = 1.803 Kb.
NEW_EXE size = 1.804 Kb.
No unusual messages during deployment.

I'm still searching but I think (not sure) there is a problem with an
external
interface (a DLL).
I'm working on it.

Regards Bruno

PS: Here's Windows Error Report (i do not know if it useful)

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="Plan 1.0.exe" FILTER="GRABMI_FILTER_PRIVACY">
    <MATCHING_FILE NAME="CGZipLibrary.dll" SIZE="57344"
CHECKSUM="0xDA9ADEE8" BIN_FILE_VERSION="1.0.0.0"
BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.00" COMPANY_NAME="CodeGuru"
PRODUCT_NAME="CGZipLibrary" FILE_VERSION="1.00"
ORIGINAL_FILENAME="CGZipLibrary.dll" INTERNAL_NAME="CGZipLibrary"
VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2"
MODULE_TYPE="WIN32" PE_CHECKSUM="0x10034" LINKER_VERSION="0x10000"
UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0"
LINK_DATE="08/02/1999 15:11:48" UPTO_LINK_DATE="08/02/1999 15:11:48"
VER_LANGUAGE="Inglés (Estados Unidos) [0x409]" />
    <MATCHING_FILE NAME="OmniBase.exe" SIZE="1841364" CHECKSUM="0xAE1CFFF7"
BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1,
0, 0, 0" COMPANY_NAME="WalicXe &lt;www.walicxe.com&gt;" PRODUCT_NAME="Plan"
FILE_VERSION="1, 0, 0, 0" ORIGINAL_FILENAME="OmniBase.exe"
LEGAL_COPYRIGHT="Copyright © 2003 WalicXe." VERFILEDATEHI="0x0"
VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32"
PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0"
UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="04/08/2003 17:14:39"
UPTO_LINK_DATE="04/08/2003 17:14:39" VER_LANGUAGE="Inglés (Estados Unidos)
[0x409]" />
    <MATCHING_FILE NAME="Plan 1.0 - Backup.exe" SIZE="1846208"
CHECKSUM="0xAE1CFFF7" BIN_FILE_VERSION="1.0.0.0"
BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1, 0, 0, 0"
COMPANY_NAME="WalicXe &lt;www.walicxe.com&gt;" PRODUCT_NAME="Plan"
FILE_VERSION="1, 0, 0, 0" ORIGINAL_FILENAME="Plan 1.0.exe"
LEGAL_COPYRIGHT="Copyright © 2003 WalicXe." VERFILEDATEHI="0x0"
VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32"
PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0"
UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="04/08/2003 17:14:39"
UPTO_LINK_DATE="04/08/2003 17:14:39" VER_LANGUAGE="Inglés (Estados Unidos)
[0x409]" />
    <MATCHING_FILE NAME="Plan 1.0.exe" SIZE="1911259" CHECKSUM="0xAE1CFFF7"
BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1,
0, 0, 0" COMPANY_NAME="WalicXe &lt;www.walicxe.com&gt;" PRODUCT_NAME="Plan"
FILE_VERSION="1, 0, 0, 0" ORIGINAL_FILENAME="Plan 1.0.exe"
LEGAL_COPYRIGHT="Copyright © 2003 WalicXe." VERFILEDATEHI="0x0"
VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32"
PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0"
UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="04/08/2003 17:14:39"
UPTO_LINK_DATE="04/08/2003 17:14:39" VER_LANGUAGE="Inglés (Estados Unidos)
[0x409]" />
    <MATCHING_FILE NAME="Unzip32.dll" SIZE="143360" CHECKSUM="0x34FD3287"
BIN_FILE_VERSION="1.1.0.0" BIN_PRODUCT_VERSION="3.0.0.0"
PRODUCT_VERSION="5.4" FILE_DESCRIPTION="Info-ZIP's UnZip DLL for Win32"
COMPANY_NAME="Info-ZIP" PRODUCT_NAME="Info-ZIP's UnZip Windows DLL"
FILE_VERSION="5.4" ORIGINAL_FILENAME="UNZIP32.DLL" INTERNAL_NAME="UnZip32"
LEGAL_COPYRIGHT="Info-ZIP 1996-1998" VERFILEDATEHI="0x0" VERFILEDATELO="0x0"
VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.1.0.0"
UPTO_BIN_PRODUCT_VERSION="3.0.0.0" LINK_DATE="12/02/1998 17:11:03"
UPTO_LINK_DATE="12/02/1998 17:11:03" VER_LANGUAGE="Inglés (Estados Unidos)
[0x409]" />
    <MATCHING_FILE NAME="wxres.dll" SIZE="2060288" CHECKSUM="0xB6F531DC"
MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
LINK_DATE="08/14/2003 00:47:55" UPTO_LINK_DATE="08/14/2003 00:47:55" />
    <MATCHING_FILE NAME="zip32.dll" SIZE="133120" CHECKSUM="0x5CE66E9E"
BIN_FILE_VERSION="1.1.0.0" BIN_PRODUCT_VERSION="3.0.0.0"
PRODUCT_VERSION="2.2" FILE_DESCRIPTION="Info-ZIP's Zip dll"
COMPANY_NAME="Info-ZIP" PRODUCT_NAME="Info-ZIP's WiZ" FILE_VERSION="2.2"
ORIGINAL_FILENAME="ZIP32.DLL" INTERNAL_NAME="Zip32"
LEGAL_COPYRIGHT="Info-ZIP 1997" VERFILEDATEHI="0x0" VERFILEDATELO="0x0"
VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.1.0.0"
UPTO_BIN_PRODUCT_VERSION="3.0.0.0" LINK_DATE="01/31/1998 03:25:20"
UPTO_LINK_DATE="01/31/1998 03:25:20" VER_LANGUAGE="Inglés (Estados Unidos)
[0x409]" />
    <MATCHING_FILE NAME="dll\gsdll32.dll" SIZE="3907640"
CHECKSUM="0x2ADE1B65" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
LINKER_VERSION="0x0" LINK_DATE="11/21/2002 11:13:39"
UPTO_LINK_DATE="11/21/2002 11:13:39" />
    <MATCHING_FILE NAME="dll\wmonnt.dll" SIZE="45056" CHECKSUM="0x34EB8097"
MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
LINK_DATE="02/06/2003 19:57:44" UPTO_LINK_DATE="02/06/2003 19:57:44" />
    <MATCHING_FILE NAME="dll\wxres.dll" SIZE="2060288" CHECKSUM="0xB6F531DC"
MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
LINK_DATE="08/14/2003 00:47:55" UPTO_LINK_DATE="08/14/2003 00:47:55" />
    <MATCHING_FILE NAME="stubFile\PlanGUIToGo.exe" SIZE="245760"
CHECKSUM="0xAE1CFFF7" BIN_FILE_VERSION="1.0.0.1"
BIN_PRODUCT_VERSION="1.0.0.1" PRODUCT_VERSION="1, 0, 0, 1"
FILE_DESCRIPTION="Dolphin XP ToGo Application" COMPANY_NAME=""
PRODUCT_NAME="A Dolphin XP ToGo Application" FILE_VERSION="1, 0, 0, 1"
ORIGINAL_FILENAME="GUIToGo.exe" INTERNAL_NAME="" LEGAL_COPYRIGHT="Portions
Copyright © Object Arts 1997-2003." VERFILEDATEHI="0x0" VERFILEDATELO="0x0"
VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.1"
UPTO_BIN_PRODUCT_VERSION="1.0.0.1" LINK_DATE="04/08/2003 17:14:39"
UPTO_LINK_DATE="04/08/2003 17:14:39" VER_LANGUAGE="Inglés (Estados Unidos)
[0x409]" />
    <MATCHING_FILE NAME="stubFile\WxGUIToGo.exe" SIZE="245760"
CHECKSUM="0xAE1CFFF7" BIN_FILE_VERSION="1.0.0.1"
BIN_PRODUCT_VERSION="1.0.0.1" PRODUCT_VERSION="1, 0, 0, 1"
FILE_DESCRIPTION="Dolphin XP ToGo Application" COMPANY_NAME=""
PRODUCT_NAME="A Dolphin XP ToGo Application" FILE_VERSION="1, 0, 0, 1"
ORIGINAL_FILENAME="GUIToGo.exe" INTERNAL_NAME="" LEGAL_COPYRIGHT="Portions
Copyright © Object Arts 1997-2003." VERFILEDATEHI="0x0" VERFILEDATELO="0x0"
VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.1"
UPTO_BIN_PRODUCT_VERSION="1.0.0.1" LINK_DATE="04/08/2003 17:14:39"
UPTO_LINK_DATE="04/08/2003 17:14:39" VER_LANGUAGE="Inglés (Estados Unidos)
[0x409]" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="kernel32.dll" SIZE="979968" CHECKSUM="0x977818F5"
BIN_FILE_VERSION="5.1.2600.0" BIN_PRODUCT_VERSION="5.1.2600.0"
PRODUCT_VERSION="5.1.2600.0" FILE_DESCRIPTION="DLL de cliente API BASE de
Windows NT" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Sistema
operativo Microsoft® Windows®" FILE_VERSION="5.1.2600.0
(xpclient.010817-1148)" ORIGINAL_FILENAME="kernel32"
INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="Copyright (C) Microsoft
Corporation. Reservados todos los derechos." VERFILEDATEHI="0x0"
VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2"
MODULE_TYPE="WIN32" PE_CHECKSUM="0xF4F64" LINKER_VERSION="0x50001"
UPTO_BIN_FILE_VERSION="5.1.2600.0" UPTO_BIN_PRODUCT_VERSION="5.1.2600.0"
LINK_DATE="08/22/2001 21:12:24" UPTO_LINK_DATE="08/22/2001 21:12:24"
VER_LANGUAGE="Español (alfabetización internacional) [0xc0a]" />
</EXE>
</DATABASE>



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.648 / Virus Database: 415 - Release Date: 31/03/2004


Reply | Threaded
Open this post in threaded view
|

Re: .EXE crash

Bill Schwab-2
Bruno,

> No EXEName.errors has been generated.

It might be a good idea to test the crash dump to ensure that it is enabled.
There are times when it can't work, or at least can't generate anything
useful (crashes on overlapped threads come to mind, and maybe others), but
it is a great tool.


> OLD_EXE size = 1.803 Kb.
> NEW_EXE size = 1.804 Kb.

You might want to check for zombie views.  Under the right circumstances,
they can make a mess of things.


> I'm still searching but I think (not sure) there is a problem with an
> external
> interface (a DLL).
> I'm working on it.

That is a very viable explanation.  However, I would first ensure that the
crash dump is enabled (if nothing else, for any future problems you might
encounter), purge zombies, and redeploy.

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: .EXE crash

Bruno Buzzi Brasesco
Hi,

Well i found it. My personal #logError: implementation does not work with
5.1.4, later i will check why ?.

Now the application is working ok, with the standart log report.

> That is a very viable explanation.  However, I would first ensure that the
> crash dump is enabled.

Where can i check this ?

Thanks a lot.

Regards
Bruno



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.648 / Virus Database: 415 - Release Date: 31/03/2004


Reply | Threaded
Open this post in threaded view
|

Re: .EXE crash

Ian Bartholomew-19
Bruno,

>> That is a very viable explanation.  However, I would first ensure
>> that the crash dump is enabled.
>
> Where can i check this ?

It's a registry entry

To check if it's on (from a Dolphin workspace)...

(((RegKey localMachineRoot at: 'Software') at: 'Object Arts') at: 'Dolphin
Smalltalk 5.0') includesKey: 'CrashDump'

To turn it on...

(((RegKey localMachineRoot at: 'Software') at: 'Object Arts') at: 'Dolphin
Smalltalk 5.0') createKey: 'CrashDump'

To turn it off...

(((RegKey localMachineRoot at: 'Software') at: 'Object Arts') at: 'Dolphin
Smalltalk 5.0') removeKey: 'CrashDump'

On a new machine that has never seen Dolphin 5.0 (as opposed to 5.1) you may
need to create the root key first...

((RegKey localMachineRoot at: 'Software') at: 'Object Arts') createKey:
'Dolphin Smalltalk 5.0'

Or you can edit/look in the registry itself of course :-)

--
Ian

Use the Reply-To address to contact me.
Mail sent to the From address is ignored.


Reply | Threaded
Open this post in threaded view
|

Re: .EXE crash

Bill Schwab-2
Bruno,

> > Where can i check this ?

In addition to Ian's very interesting answer, see #crashDump:.  It will
allow you to force a dump to verify that the output gets generated and that
it goes where you expect.

Ian,

Great stuff!  It would be _really_ slick if the version numbers came from
SessionManager.  Then we would have a way for any Dolphin image to get/set
its dump configuration.

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: .EXE crash

Ian Bartholomew-19
Bill,

> Great stuff!  It would be _really_ slick if the version numbers came
> from SessionManager.  Then we would have a way for any Dolphin image
> to get/set its dump configuration.

I had a minimal (and I mean minimal) goodie that did that but it became a
bit problematic (see below) so I dumped it.  I keep the scripts in a file
now so it's just as easy :-)

The problem with using SessionManager>>productVersion is that it answers 5.1
but the current crash dump implementation still looks for a key at 5.0.  I
decided it wasn't worth the trouble of fiddling  about to check/create the
extra registry entry (it would hve doubled the size of the goodie package
:-) ) so I dropped it.

FWIW I very rarely, if ever, need to turn off the crash dump anyway and IIRC
it would normally be turned on by default.  It's only the problem with the
old registry entry that is causing  problems at the moment.

Roll on D6

--
Ian

Use the Reply-To address to contact me.
Mail sent to the From address is ignored.


Reply | Threaded
Open this post in threaded view
|

Re: .EXE crash

Bruno Buzzi Brasesco
In reply to this post by Ian Bartholomew-19
The crush dump is enabled.
The problem was my 5.1.2 old implementation of #logError:.

Thanks Ian and Bill.


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.648 / Virus Database: 415 - Release Date: 31/03/2004