[Openmcl-devel] Problem with gtk2 on Linux/PPC
gb at clozure.com
Wed Apr 13 13:54:18 EDT 2005
On Wed, 13 Apr 2005 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.
This doesn't address the problem exactly (I'll try to respond to your
later message soon), but you can get GDB to be a -bit- quieter when
debugging OpenMCL by getting it to load (or "source", as a verb)
the file ccl/lisp-kernel/PLATFORM/.gdbinint.
One Linux, there's still an issue having to do with what Unix
signals are generated by PPC trap instructions. OpenMCL code
contains sequences like:
(twlllt allocptr,allocbase) ; trap if this thread needs more room to
; cons in
That generates a SIGTRAP signal; GDB mistakenly believes that all
SIGTRAP signals must have something to do with its breakpoints, and
gets confused when it starts to learn that this isn't the case. There
may be a way of patching GDB to eliminate this confusion; it's often
simpler to patch the bit of the Linux kernel that maps PPC exceptions
to Unix signals to generate some other signal (SIGILL) in this case.
(There are some other Linux-specific issues on recent Linux versions;
that would be an even longer, further off-topic message.)
I'll try to look at gtk2 under Linux in a bit.
> Thanks Ralf Mattes
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
More information about the Openmcl-devel