newbie question.

I am a complete newbie to lips and CMUCL.  I have two
problems that I need
your help with.

First, I'm having problems with launching the debugger on
my ubuntu 64 box.


Second, I'm having problems with loading uffi library.

See the output below.

Can any of you give me some clues as how to fix both these
problems?

Thanks in advance.

Yarek

yarekubuntu:/usr/share/common-lisp/systems$ lisp
CMU Common Lisp 19c (19C), running on ubuntu
With core: /usr/bin/lisp.core
Dumped on: Wed, 2006-08-23 11:17:38-07:00 on ubuntu
See <http://www.cons.org/cm
ucl/> for support information.
Loaded subsystems:
    Python 1.1, target Intel x86
    CLOS based on Gerd's PCL 2004/04/14 03:32:47
    Gray Streams Protocol Support
    CLX X Library MIT R5.02
    Motif toolkit and graphical debugger 1.0
    Hemlock 3.5
*  (asdf:oos `asdf:load-op :uffi)

; loading system definition from uffi.asd into #<The
ASDF1788 package>
; Loading
#P"/usr/share/common-lisp/source/uffi/uffi.asd".
; registering #<SYSTEM UFFI > as UFFI
; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. O C):
; Compiling Top-Level Form:
Invoking debugger...
Starting server:
   will_fork  = False
   will_trace = False
   No Inet domain socket created.
   path       = /tmp/.motif_socket-p5
Waiting for connection.

>>>>> "Yarek" == Yarek Kowalik
<yarek.kowalikgmail.com> writes:

    Yarek> I am a complete newbie to lips and CMUCL.  I
have two problems that I need
    Yarek> your help with.

    Yarek> First, I'm having problems with launching the
debugger on my ubuntu 64 box.

There have been some issues the version of the motif
(Lesstif version
x) library I use to build motifd.   Unfortunately, I can't
easily
upgrade my box to something different.

So as a work around, you can either use a core with the
motif toolkit
and debugger, or you can do (setf interfaceinterface-st
yle* :tty) to
turn off the graphical debugger.  (I think.)

    Yarek> Second, I'm having problems with loading uffi
library.

Fixing the above will at least get you to the debugger where
we can
figure out what's going on.  I haven't built uffi in a
while, but it
worked for me.  Perhaps the uffi library is building a
64-bit version
but cmucl only works with a 32-bit version?

Ray

I recompiled motifd using Open Motif on my Ubuntu 64 box (I
did use the
header files you sent to me eariler).  Is there any way I
can test if motifd
is working OK?

What does it mean "use a core with the motif toolkit
and debugger"?

If I ware to use TTy debugger, do I need to launch a
separate debugger
process, or will the debuggin session begin automatically at
the point of
the error detection within the current lisp session?

Thanks,

Yarek

On 9/13/06, Raymond Toy <raymond.toyericsson.com> wrote:
>
> >>>>> "Yarek" == Yarek
Kowalik <yarek.kowalikgmail.com> writes:
>
>     Yarek> I am a complete newbie to lips and CMUCL.
 I have two problems
> that I need
>     Yarek> your help with.
>
>     Yarek> First, I'm having problems with
launching the debugger on my
> ubuntu 64 box.
>
> There have been some issues the version of the motif
(Lesstif version
> x) library I use to build motifd.   Unfortunately, I
can't easily
> upgrade my box to something different.
>
> So as a work around, you can either use a core with the
motif toolkit
> and debugger, or you can do (setf interfaceinterface-st
yle* :tty) to
> turn off the graphical debugger.  (I think.)
>
>     Yarek> Second, I'm having problems with loading
uffi library.
>
> Fixing the above will at least get you to the debugger
where we can
> figure out what's going on.  I haven't built uffi in
a while, but it
> worked for me.  Perhaps the uffi library is building a
64-bit version
> but cmucl only works with a 32-bit version?
>
> Ray
>
>

>>>>> "Yarek" == Yarek Kowalik
<yarek.kowalikgmail.com> writes:

    Yarek> I recompiled motifd using Open Motif on my
Ubuntu 64 box (I did use the
    Yarek> header files you sent to me eariler).  Is
there any way I can test if motifd
    Yarek> is working OK?

I rarely use it, but since you have clm (motif) in your core
already,
just press Ctrl-D at the repl.  When I do this, I get:

    * ^CInvoking debugger...
    Starting server:
       will_fork  = False
       will_trace = False
       No Inet domain socket created.
       path       = /tmp/.motif_socket-p9198
    Waiting for connection.
    Accepting client on Unix socket.
    Accepted client on fd 4
    Server not forking.

and a Debugger window pops up.

    Yarek> What does it mean "use a core with the
motif toolkit
    Yarek> and debugger"?

Oops.  I meant don't use a core with the motif toolkit.  It
seems
you're using the binaries from c-l.net, so you've created
a core with
gray streams, clx, clm, and hemlock.  If so, you can use the
standard
core that binaries from cl.net provide.

    Yarek> If I ware to use TTy debugger, do I need to
launch a separate debugger
    Yarek> process, or will the debuggin session begin
automatically at the point of
    Yarek> the error detection within the current lisp
session?

With the tty debugger, you'll get to the debugger right in
the same
window.  Pressing Ctrl-D at the repl will give you something
like:

    * (setf interfaceinterface-st
yle* :tty)

    :TTY
    * ^C
    Interrupted at #xFF21DBE4.
       [Condition of type SIMPLE-CONDITION]

    Restarts:
      0: [CONTINUE] Return from BREAK.
      1: [ABORT   ] Return to Top-Level.

    Debug  (type H for help)

    (UNIX::SIGINT-HANDLER #<unused-arg>
#<unused-arg> #.(SYSTEM:INT-SAP #xFFBEE240))
    Source: 
    ; File: target:code/signal.lisp
    (DEFINE-SIGNAL-HANDLER SIGINT-HANDLER
"Interrupted" BREAK)
    0] 

You're in the tty debugger now.

Ray