SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 27 | April | 2008 ]

<< Previous Message << >> Next Message >>


Date: Sun, 27 Apr 2008 22:14:18 -0700
From: Sandy <sshapiro@ucsd.edu >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Seamonkey


1
This is a multi-part message in MIME format.

Content Type: text/plain

Content-Transfer-Encoding: 7bit

Steven Levine wrote:
>
> This means the code detected a should not occur error and sorta threw up
> its hands.
>
> My first suspect for this kind of failure would be a corrupted font.
> Unfortunately, these are difficult to track down.
>
>
Any suggestions that I can try?
>>
>
> This tends to happen for some kinds of errors. In particular stack
> overflow exceptions can cause this. The kernel needs a certain amount of
> available stack that the process owns to run the code that formats the
> traps screens.
>
>
>
Anything I can do to improve that situation?

Thanks,
Sandy


Content Type: text/html

Content-Transfer-Encoding: 7bit Steven Levine wrote:


This means the code detected a should not occur error and sorta threw up
its hands.

My first suspect for this kind of failure would be a corrupted font. 
Unfortunately, these are difficult to track down.

  
Any suggestions that I can try?

  
    

This tends to happen for some kinds of errors.  In particular stack
overflow exceptions can cause this.  The kernel needs a certain amount of
available stack that the process owns to run the code that formats the
traps screens.


  
Anything I can do to improve that situation?

Thanks,
Sandy


Content Type: text/plain

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"postmaster@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 27 | April | 2008 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.