[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GDNC crashes
Re: GDNC crashes
Fri, 17 Aug 2001 13:47:38 +0000
On Friday, August 17, 2001, at 07:13 PM, Marko Mikulicic wrote:
I use libffi becouse libfcall does fails with gstep-db (EOFaul class).
That surprises me ... ,y understanding is that the libffi code is
but that the libffcall code is pretty solid ... though a memory leak was
fixed a while
back, and a threading problem quite recently.
I suspect that if the libffcall/gstep-db combination fails, the bug is
most likely in
gstep-db and the libffi stuff is hiding it in some way.
I used gnustep with libffi for 4 days without problems then I rebooted
my machine, rebuild the font cache (I added latin2 fonts on the system
and I wanted to try them out on gnustep) wich leaded to a xfs crash
(Xfree 4.0.3). After that I sucessfully started an *.app but
the NSWorkspaceDidLaunchApplicationNotification crashed gdnc.
My guess is that you were using a version of gdnc linked with libffcall,
and after the reboot used libffi, and the libffi stuff isn't working yet.
Is gdnc requred also for non distributed code ? (All I want
is a database oriented application that doesn't need interact
with other applications, for now)
NSWorkspace uses it to let other apps (and the workspace manager) know
about the app.
Is there a quick hack that prevents gnustep from using gdnc ?
Commenting out the code that uses the distributed notification center in
NSWorkspace.m should probably work to stop your apps using this.
That being said, I'd recommend getting the latest code from CVS (or a
if that's easier) and using libffcall.
- GDNC crashes, Marko Mikulicic, 2001/08/17
- Re: GDNC crashes,
Richard Frith-Macdonald <=