>>>>> "Yarek" == Yarek Kowalik <[EMAIL PROTECTED]> 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 interface:*interface-style* :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
