[erlang-patches] Strange thing in lib/kernel/src/group.erl

Siri Hansen <>
Thu Jan 9 10:48:02 CET 2014


Hello,

this patch has been converted to a bug-report and a ticket is created and
placed in our backlog. The reason for this is that we believe the matter
needs further investigation, which we have not been able to make time for
yet. The ticket will be prioritized along with the rest of the items in our
backlog.

Thanks for your contribution!

Best Regards
/siri




2013/5/16 Stefan Zegenhagen <>

> Dear all,
>
> since the discussion seems to have gotten quiet, I've prepared a patch
> to restart the discussion of this topic.
>
> In an interactive shell, the shell process has no means to reliably get
> the exit reason of the associated user_drv and, therefore, cannot
> meaningfully react on errors reported by the user_drv. However, it
> occasionally is required to know why an interactive shell session was
> terminated.
>
> The patch attached to this e-mail solves the issue by always propagating
> the exit reason of the user_drv to the shell process. In summary, the
> patch does the following:
>
>       * propagate the correct exit reason of the user_drv to the shell
>         under all circumstances
>       * always make sure that the shell process terminates when the
>         user_drv has exited
>       * give the shell process two seconds time to react on the exit
>         signal before forcedly killing it
>
> Shell processes using I/O functionality from the io.erl module will be
> largely unaffected because io.erl catches exits of the group_leader()
> during io_requests and translates them to {error, terminated} error
> codes (independent of the exit reason found in the exit signal). Shell
> processes implementing the I/O protocol themselfs might experience
> unexpected 'EXIT' reasons.
>
> The patch makes sure that shell is forcedly killed as before, it only
> gives the shell process a little time to terminate itself before doing
> so. It also makes sure that the shell is killed under *ALL*
> circumstances, not just while some I/O client is waiting for input.
>
>
> Kind regards,
>
> --
> Dr. Stefan Zegenhagen
>
> arcutronix GmbH
> Garbsener Landstr. 10
> 30419 Hannover
> Germany
>
> Tel:   +49 511 277-2734
> Fax:   +49 511 277-2709
> Email: 
> Web:   www.arcutronix.com
>
> *Synchronize the Ethernet*
>
> General Managers: Dipl. Ing. Juergen Schroeder, Dr. Josef Gfrerer -
> Legal Form: GmbH, Registered office: Hannover, HRB 202442, Amtsgericht
> Hannover; Ust-Id: DE257551767.
>
> Please consider the environment before printing this message.
>
> _______________________________________________
> erlang-patches mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-patches
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-patches/attachments/20140109/280b9e67/attachment.html>


More information about the erlang-patches mailing list