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


sr #109380: Specificity of error type on broken pipe

Submitted by:  Martin Saturka <kvutza>
Submitted on:  Tue 05 Sep 2017 12:22:26 AM UTC  
Category: NonePriority: 5 - Normal
Severity: 3 - NormalStatus: None
Privacy: PublicAssigned to: None
Open/Closed: OpenOperating System: None

Add a New Comment(Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


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 File(s):

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


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

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.


    Please enter the title of George Orwell's famous dystopian book (it's a date):



    No Changes Have Been Made to This Item

    Back to the top

    Powered by Savane 3.1-cleanup1