(no subject)

Re: (no subject)

F D <dubfa <at> hotmail.com> writes:

> Hello,
>
> I would like to use slime as a debugger for an application created from lispworks.
> Does anyone already do that but with a password protection?
> To use the debugger (or any other slime), one will have to enter a password to be connected to the application.
>  I don't want to open a port on this application without any protection. 
Remote (as in through unsecure networks not under your control)
communication is usually done through SSH tunnels.

--

-- 
With best regards, Stas.

Re: (no subject)

Hi Fabien,

If I understand your question correctly,do you want a secure slime connection?

slime will listen default on 127.0.0.1, and you can connect it remotely by a ssh tunnel like this:

   ssh -l username -L 4005:localhost:4005 slime-host 

So no extra port is needed to connect to your slime.   

Hope it helpful.

> Hello,
> 
> I would like to use slime as a debugger for an application created from lispworks.
> Does anyone already do that but with a password protection?
> To use the debugger (or any other slime), one will have to enter a password to be
> connected to the application.
>  I don't want to open a port on this application without any protection.
> 
> Many Thanks
> 
> Fabien
> 
___________________________________
Jingtao Xu
A Lisp Programmer
www.jingtao.net

Re: (no subject)

Stas Boukarev <stassats <at> gmail.com> writes:

> F D <dubfa <at> hotmail.com> writes:
>
>> Hello,
>>
>> I would like to use slime as a debugger for an application created from lispworks.
>> Does anyone already do that but with a password protection?
>> To use the debugger (or any other slime), one will have to enter a password to be connected to the application.
>>  I don't want to open a port on this application without any protection. 
> Remote (as in through unsecure networks not under your control)
> communication is usually done through SSH tunnels.
And for local connection, swank listens on 127.0.0.1 by default.

--

-- 
With best regards, Stas.

ELS 2012, Zadar, Croatia

Apologies for the multiple postings. 

PAPER SUBMISSION DEADLINE EXTENDED 

European Lisp Symposium 2012, Zadar, Croatia, April 30th - May 1st, 2012 

http://european-lisp-symposium.org 

The purpose of the European Lisp Symposium is to provide a forum for 
the discussion and dissemination of all aspects of design, 
implementation and application of any of the Lisp and Lisp-inspired 
dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, 
Dylan, Clojure, ACL2, ECMAScript, Racket, SKILL, and so on. We 
encourage everyone interested in Lisp to participate. 

The main theme of the 2012 European Lisp Conference is 
"Interoperability: Systems, Libraries, Workflows".  Lisp based and 
functional-languages based systems have grown a variety of solutions 
to become more and more integrated with the wider world of Information 
and Communication Technologies in current use.  There are several 
dimensions to the scope of the solutions proposed, ranging from 
"embedding" of interpreters in C-based systems, to the development of 
abstractions levels that facilitate the expression of complex context 
dependent tasks, to the construction of exchange formats handling 
libraries, to the construction of theorem-provers for the "Semantic 
Web".  The European Lisp Symposium 2012 solicits the submission of 
papers with this specific theme in mind, alongside the more 
traditional tracks which have appeared in the past editions. 

We invite submissions in the following forms: 

Papers: Technical papers of up to 15 pages that describe original 
results or explain known ideas in new and elegant ways. 

Demonstrations: Abstracts of up to 4 pages for demonstrations of 
tools, libraries, and applications. 

Tutorials: Abstracts of up to 4 pages for in-depth presentations about 
topics of special interest for at least 90 minutes and up to 180 
minutes. 

Lightning talks: Abstracts of up to one page for talks to last for no 
more than 5 minutes. 

All submissions should be formatted following the ACM SIGS guidelines 
and include ACM classification categories and terms. For more 
information on the submission guidelines and the ACM keywords, see: 
http://www.acm.org/sigs/publications/proceedings-templates and 
http://www.acm.org/about/class/1998. 

Important dates: 

February 15th 2012: submission deadline (extended deadline) 
March 7th 2012: acceptance results 

April 30th 2012: Conference opens 

Program Commitee. 
Chair: 
Marco Antoniotti, Università degli Studi di Milano Bicocca, Milan, ITALY 

Local organizers: 
Damir Cavar, Eastern Michigan University 
Franjo Pehar, University of Zadar 
Damir Kero, University of Zadar 

Members: 
Giuseppe Attardi, Università degli Studi di Pisa, Pisa, ITALY 
Pascal Costanza, Intel, Bruxelles, BELGIUM 
Marc Feeley, Université de Montreal, Montreal, CANADA 
Scott McKay, Google, U.S.A. 
Kent Pitman, U.S.A. 
Christophe Rhodes, Department of Computing, Goldsmiths, University of London, London, UNITED KINGDOM 
Robert Strandh, LABRI, Université de Bordeaux, Bordaux, FRANCE 
Didier Verna, EPITA / LRDE, FRANCE 
Taiichi Yuasa, Kyoto University, JAPAN

--
Marco Antoniotti

Not using Slime's debugger

Hi,

I want to use my own debugger function. Normally I do this by setting a
custom function designator to cl:*debugger-hook*. With Slime I can't do
this automatically because swank sets it to #'swank:swank-debugger-hook.

The Slime manual says that ~/.swank.lisp can be used for setting
swank:*global-debugger* to nil. Even if I do this, cl:*debugger-hook* is
still set to swank's function.

Is there a way to set custom debugger automatically with Slime? Mostly I
use SBCL.

Re: Not using Slime's debugger

* Teemu Likonen [2012-02-05 18:38] writes:

> Hi,
>
> I want to use my own debugger function. Normally I do this by setting a
> custom function designator to cl:*debugger-hook*. With Slime I can't do
> this automatically because swank sets it to #'swank:swank-debugger-hook.
>
> The Slime manual says that ~/.swank.lisp can be used for setting
> swank:*global-debugger* to nil. Even if I do this, cl:*debugger-hook* is
> still set to swank's function.

Works for me: the gobal value of *debugger-hook* is nil.  SLIME still
dynamically binds it while processing it's own requests.

> Is there a way to set custom debugger automatically with Slime? Mostly I
> use SBCL.

Not that I know of.

Helmut

Re: Not using Slime's debugger

* Helmut Eller [2012-02-05 20:52:41 +0100] wrote:

> * Teemu Likonen [2012-02-05 18:38] writes:
>> I want to use my own debugger function. Normally I do this by setting
>> a custom function designator to cl:*debugger-hook*. With Slime I
>> can't do this automatically because swank sets it to
>> #'swank:swank-debugger-hook.
>>
>> The Slime manual says that ~/.swank.lisp can be used for setting
>> swank:*global-debugger* to nil. Even if I do this, cl:*debugger-hook*
>> is still set to swank's function.
>
> Works for me: the gobal value of *debugger-hook* is nil. SLIME still
> dynamically binds it while processing it's own requests.

Ah, separate binding, indeed. In *inferior-lisp* buffer *debugger-hook*
variable is NIL and in Slime-REPL buffer it's swank's debugger function.

>> Is there a way to set custom debugger automatically with Slime?
>> Mostly I use SBCL.
>
> Not that I know of.

OK, thanks. I ended up redefining swank:swank-debugger-hook function in
~/.swank.lisp file. It's a bit ugly but does what I want.

My "debugger" just prints the condition type, available restarts and
error message. Then it invokes ABORT restart automatically. I don't need
Slime's debugger because SBCL does not give much useful information
there anyway (even with the highest debugging level).

Not using Slime's debugger 2

Re: Not using Slime's debugger 2

* Mark H. David [2012-02-06 12:52:04 -0500] wrote:

> What am I missing?

You probably didn't read my nor Helmut's recent messages too closely.
Anyway, here's the code I'm using.

;; ~/.swank.lisp

(defpackage #:personal
  (:use #:cl)
  (:export #:debugger #:*use-swank-debugger*))

(in-package #:personal)

;; This variable is used to switch betwee swank and custom debugger
;; function.
(defparameter *use-swank-debugger* nil)

(defvar *swank-debugger-orig* #'swank:swank-debugger-hook)

;; Custom "debugger" (just prints condition, restarts and error message.)
(defun debugger (condition previous)
  (declare (ignore previous))
  (with-standard-io-syntax
    (let ((*print-readably* nil)
          (*print-length* 50)
          (*print-level* 5))
      (format *error-output*
              "~%; Condition: ~A~%; Restarts:  ~{~A~^ ~}~%; ~A~%"
              (type-of condition) (mapcar #'restart-name (compute-restarts))
              condition)
      (invoke-restart 'abort))))

;; Redefine swank's debugger function.
(defun swank:swank-debugger-hook (condition previous)
  (if *use-swank-debugger*
      (funcall *swank-debugger-orig* condition previous)
      (funcall 'debugger condition previous)))