newlispfanclub.alh.net

Hi Lutz,

Starting the help from the newlisp-edit brought me this fine error,
just as a notification that java can crash too ;-)..

Im checking the error currently ..


#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0x45a8b2eb, pid=6191, tid=262161
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_09-b01 mixed mode, sharing)
# Problematic frame:
# C [libfontmanager.so+0x2d2eb]
#
# An error report file with more information is saved as hs_err_pid6191.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#

Hi Lutz,

It keep coming these errors since GS 1.05..

every time i select i.e. font-select from the editor ..it crashes..
or if I click help.. I already deleted the .newlisp-edit* files from the home dir
but that did not help....odd...? any idea?

PS the JAVA log is very very big.. if you want it I can post it..


newLISP-GS v.1.05
double buffering supported.
listening on 47011
accepted connection from 0.0.0.0
connecting to 0.0.0.0:47012
retrying to connect
server connected
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0x45a88d7b, pid=11420, tid=262161
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_09-b01 mixed mode, sharing)
# Problematic frame:
# C [libfontmanager.so+0x2ad7b]
#
# An error report file with more information is saved as hs_err_pid11420.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#

During all the devlopment of guiserver.jar the JVM has never crashed on me (Mac OS X). The error seems to have its origin in libfontmanager.so, a Linux X-Windows system library? I would send the error log to Sun.

Lutz

Now I remember Michael having had a similar problem on OS X. After removing a specific font it stopped crashing. It happened when trying to set/use that font.

Load all fonts using gs:get-fonts, then try them out one by one. You could start out with the allfonts-demo.lsp and put a (println ...) statement in to the (dolist ...) where it sets the fonts. Or just turn the trace on and see on which font it bombs.

Lutz

I think i know the problem, its indeed a font issue!
I had a fresh linux install and dont have the extented font yet.. ;-)
ill check it again when done..