[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #62030] 'Malformed xchar' error, if fork'ed child throws
From: |
Stephan Rudlof |
Subject: |
[bug #62030] 'Malformed xchar' error, if fork'ed child throws |
Date: |
Fri, 11 Feb 2022 21:16:45 -0500 (EST) |
Follow-up Comment #6, bug #62030 (project gforth):
[comment #4 comment #4:]
> I added a bit code for handling a closed stdin more gracefully.
Sounds good: it's good, if an uncatched throw does not end in an endless
loop... (shit happens); especially if it's a new effect in comparison with the
official version.
> The recommended way to handle forked instances is still to use exit() to
leave them, and never let a throw return to the QUIT loop.
OK (if not '(bye)').
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?62030>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [bug #62030] 'Malformed xchar' error, if fork'ed child throws, Stephan Rudlof, 2022/02/10
- [bug #62030] 'Malformed xchar' error, if fork'ed child throws, Anton Ertl, 2022/02/11
- [bug #62030] 'Malformed xchar' error, if fork'ed child throws, Stephan Rudlof, 2022/02/11
- [bug #62030] 'Malformed xchar' error, if fork'ed child throws, Bernd Paysan, 2022/02/11
- [bug #62030] 'Malformed xchar' error, if fork'ed child throws, Bernd Paysan, 2022/02/11
- [bug #62030] 'Malformed xchar' error, if fork'ed child throws, Stephan Rudlof, 2022/02/11
- [bug #62030] 'Malformed xchar' error, if fork'ed child throws,
Stephan Rudlof <=
- [bug #62030] 'Malformed xchar' error, if fork'ed child throws, Bernd Paysan, 2022/02/11
- [bug #62030] 'Malformed xchar' error, if fork'ed child throws, Stephan Rudlof, 2022/02/13
- [bug #62030] 'Malformed xchar' error, if fork'ed child throws, Stephan Rudlof, 2022/02/13
- [bug #62030] 'Malformed xchar' error, if fork'ed child throws, Stephan Rudlof, 2022/02/13