Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 5 Oct 2023 15:39:26 +0200
From: Szabolcs Nagy <>
To: Carl Chave <>
Cc: Rich Felker <>,
Subject: Re: Hung processes with althttpd web server

* Carl Chave <> [2023-10-04 22:43:16 -0400]:
> > 1. What Alpine/musl version are you using? If it's older, it might be
> >    something that would be different in current versions.
> Alpine 3.18.3 with musl package musl-1.2.4-r1 x86_64
> > 2. Can you attach gdb to the hung process and identify what lock
> >    object it's waiting on?
> I don't really know what I'm doing with gdb. This is probably not helpful:
> (gdb) bt
> #0  0x00007f5fb449c0dd in ?? () from /lib/
> #1  0x0000000000000002 in ?? ()
> #2  0x0000000000000000 in ?? ()

you might want to

apk add musl-dbg

the bt should be more useful then.

in this case you can also look at

(gdb) disas $rip-40,+80
(gdb) info reg

since the address is the first arg to a futex syscall (rdi).
then you can try to dig around to see where rdi points to

(gdb) x/4wx $rdi-4
(gdb) info sym $rdi


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.