-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/2/14, 12:59 PM, Darshit Shah wrote:
>> However, when I attempted the same from a virtual Terminal instead of an
>> emulator, upon remotely detaching the screen session, my terminal
>> directly displayed a login prompt again. This leads me to believe that
>> Bash did crash even then and caused the login prompt to reappear.
>>
>>
>
> I just recompiled my Bash with debugging symbols and attempted to run Bash
> under gdb. Here is the trace I received:
>
>
> [remote power detached from 19442.pts-1.mordor]
>
> Program received signal SIGHUP, Hangup.
The shell received SIGHUP, presumably sent by screen or the vty driver.
SIGHUP is a fatal signal; the shell catches it, cleans up, restores the
default signal handler, and resends SIGHUP to itself, which results in
bash exiting due to the SIGHUP.
This is not a bug.
- --
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
iEYEARECAAYFAlR+FrMACgkQu1hp8GTqdKtO8wCeLT+SAznAczjfUuko5fBmcWnm
87EAn1k4Ps7hrTGULjP+2ysstxDYeW8S
=7ZUh
-----END PGP SIGNATURE-----
