linux-kernel - Re: Advice on debuging the fork syscall hanging forever

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 25 Apr 2007 11:46:48 -0300
From:	"Miguel Freitas" <mfreitas@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: Advice on debuging the fork syscall hanging forever

On 4/25/07, Miguel Freitas <mfreitas@...il.com> wrote:
> (...)
> 0x00002b2e77d6d5b6 <fork+134>:  mov    $0x38,%eax
> 0x00002b2e77d6d5bb <fork+139>:  syscall
> 0x00002b2e77d6d5bd <fork+141>:  cmp    $0xfffffffffffff000,%rax
>
> (...)
>
> (gdb) info reg
> rax            0xfffffffffffffdff       -513

hey, could it be that this -513 is actually -ERESTARTNOINTR?
which, btw, is said to "Should never be seen by user programs" in
include/linux/errno.h?

is it leaking? ;-)

Miguel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/