mainGNU Common Lisp - Support: sr #109380, Specificity of error type on...


sr #109380: Specificity of error type on broken pipe

Submitter:  Martin Saturka <kvutza>
Submitted:  Tue 05 Sep 2017 12:22:26 AM UTC
Category:  None Priority:  5 - Normal
Severity:  3 - Normal Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open Operating System:  None
* Mandatory Fields

Add a New Comment Rich Markup

Fri 08 Sep 2017 03:25:35 PM UTC, comment #1: 

Notice that the perror(""); in the o/usig.c:sigpipe(void) function means that even when we catch this error in lisp code, we still get output at stderr that makes it messy (use of with-output-to-string (error-output) did not help me on that).

Martin Saturka <kvutza>
Tue 05 Sep 2017 12:22:26 AM UTC, original submission:  

When getting broken-pipe event in GCL session that is not ignored, the triggered error is ''internal-simple-error'' (via FEerror, at o/usig.c, sigpipe(void)) that is less specific than one could hope.

Could it be set to some more specific error type, like e.g. stream-error, please? It would be easier to decide what to do on such situations in a programmatic way then.

Martin Saturka <kvutza>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by kvutza (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.


    No changes have been made to this item

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code