[Openmcl-devel] Problem with gtk2 on Linux/PPC

rm at fabula.de rm at fabula.de
Wed Apr 13 03:22:52 PDT 2005

On Wed, Apr 13, 2005 at 10:43:33AM +0200, rm at fabula.de wrote:
> Hello list,
> i'm still trying to get the gtk2 bindings to work on
> Linux/PPC. I thought that upgrading to 14.2-bleeding might
> solve my problem (Lisp drops me into the kernel debugger
> as soon as a callback is invoked). Well, i don't get into
> the debugger any more - the system justs exits ...
> Any ideas on how i can debug this? I tried to attach gdb 
> to the running image but this doesn't really work since
> gdb constantly breaks on all sorts of signals.

Just as a follow-up: i attached gdb to the core file generated
(using an unstripped version of OpenMCL and the .gdbinit from
ccl:lisp-kernel;linux). Here's the backtrace (my indentation):

  (gdb) bt
  #0  prepare_to_wait_for_exception_lock (tcr=0xe00000, context=0x30cbe480) 
      at ../lisp-exceptions.c:1794
  #1  0x0001452c in signal_handler (signum=11, info=0x30cbe400, context=0x30cbe480, tcr=0xe00000) 
      at ../lisp-exceptions.c:1865
  #2  0x300ebbd4 in __pthread_sighandler_rt () from /lib/libpthread.so.0
  #3  <signal handler called>
  #4  <signal handler called>
  #5  <signal handler called>
  Cannot access memory at address 0x4e800024

Hmm, this is in signal-handling code  and way beyond my experience ...

  Thanks Ralf Mattes

> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel

More information about the Openmcl-devel mailing list