Article View: comp.sys.mac
Article #45937Re: Some Human Interface (was: System Error = 03)
From: Larry Rosenstein
Date: Fri, 09 Feb 1990 18:29
Date: Fri, 09 Feb 1990 18:29
21 lines
1302 bytes
1302 bytes
In article <5415@bgsuvax.UUCP> denbeste@bgsuvax.UUCP (William C.
DenBesten) writes:
> Memory Corupted id=28 DSStkNHeapHeap
> Memory Full id=25 DSMemFullErr
> Application Damaged id=16 DSBadLaunch
> Application Damaged id=15 DSLoadErr
MultiFinder does report Memory Full. id=28 could be a stack overflow
caused by a program loop or too much recursion, although the result is
definitely corrupted memory.
id=16 might make sense, but I think id=15 means that a segment couldn't be
loaded, which could be an application memory management error.
So it isn't easy to map the id codes to a meaningful error.
Larry Rosenstein, Apple Computer, Inc.
Object Specialist
Internet: lsr@Apple.com UUCP: {nsc, sun}!apple!lsr
AppleLink: Rosenstein1
Technical Details
Message-ID:
<6606@internal.Apple.COM>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!zaphod.mps.ohio-state.edu!mips!apple!Apple.COM!lsrReferences:
<33777@news.Think.COM> <5415@bgsuvax.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!zaphod.mps.ohio-state.edu!mips!apple!Apple.COM!lsr From: lsr@Apple.COM (Larry Rosenstein) Newsgroups: comp.sys.mac Subject: Re: Some Human Interface (was: System Error = 03) Message-ID: <6606@internal.Apple.COM> Date: 9 Feb 90 18:29:04 GMT Sender: usenet@Apple.COM Organization: Objects-R-Us, Apple Computer, Inc. Lines: 21 References: <33777@news.Think.COM> <5415@bgsuvax.UUCP>