scsh-hackers
[Top] [All Lists]

[Scsh-hackers] [ scsh-Bugs-408133 ] exception in host-info

To: noreply@sourceforge.net
Subject: [Scsh-hackers] [ scsh-Bugs-408133 ] exception in host-info
From: nobody <nobody@sourceforge.net>
Date: Mon, 12 Mar 2001 20:10:27 -0800
List-id: Discussion among the implementors <scsh-hackers.lists.sourceforge.net>
Sender: scsh-hackers-admin@lists.sourceforge.net
Bugs #408133, was updated on 2001-03-12 20:10
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=110493&aid=408133&group_id=10493

Category: run-time
Group: None
Status: Open
Priority: 5
Submitted By: Brian D. Carlstrom
Assigned to: Brian D. Carlstrom
Summary: exception in host-info

Initial Comment:
My first guess for why these routines behave 
differently is because they use herrno, not errno.

-bri

From: Maurice.Bremond@inria.fr
To: scsh@ai.mit.edu
Subject: exception in host-info
Date: Wed, 12 Nov 1997 15:53:44 +0100 (MET)


Our installation :
 scsh-0.5.1 on Solaris, sun Os 4, sgi

Our problem :
 We discovered that we can't catch the following 
exception :

(with-errno-handler
 ((errno packet)
  (else (list errno packet)))
 (host-info "128.93.21.99")) ; a host that doesn't 
have a DNS entry

>
Error: name->host-info: non-zero herrno ~s ~s
       1
       #f

host-info does not seem to raise any exception upon 
error, neither do almost al\
l
other procedures from network.scm (as they all call 
the alt/features.scm
error procedure instead of scsh/scsh-conditions errno-
error).

Is there any way to do avoid stopping execution in 
this case ?

Thank you in advance,

Maurice Br\351mond - INRIA France




----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=110493&aid=408133&group_id=10493


<Prev in Thread] Current Thread [Next in Thread>
  • [Scsh-hackers] [ scsh-Bugs-408133 ] exception in host-info, nobody <=