invalid address exception, it's most likely a pointer gone haywire.
Sorry, but without a debug kernel (which only exists internally in MBS),
there is no easy way to track it down.
________________________________
From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of Bayliss, Barry
Sent: Thursday, May 12, 2005 5:18 PM
To: [email protected]
Subject: [development-axapta] Understanding crash logs
Hello,
Does anyone have any references / information on how to use the
information contained in the crash log to determine if (and what) coding
modifications may be at fault?
An example of a recent crash log has been attached at the end of this
message. Note, we have not yet found a way to duplicate the crash, ie
the process may crash the 3rd time it is run by a particular user, but
not at other times, and may not crash at all for all users.
Any ideas / suggestions would be helpful.
Thanks.
Barry.
Axapta Crash Dump File for Axapta build 1951.2410 (Aug 19 2003 19:44:15)
Dumped : Wed May 11 14:46:44 2005
Crash : Exception 0xc0000005 caught (unspecified) in thread 0x488 of
process 0xe40.
-------------------------------------------------------------
--# FV EIP----- RetAddr- FramePtr StackPtr Symbol
0 .V 00551e95 0000252a 05981a94 0012e3c8 Mod: ax32[ax32.exe],
base: 00400000h
Stackdump exit code 487 (Attempt to access invalid address)
________________________________
Yahoo! Groups Links
* To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/
* To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]
be>
* Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/> .
[Non-text portions of this message have been removed]
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
