mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: Carl Chave <online@chave.us>
Cc: Rich Felker <dalias@libc.org>, musl@lists.openwall.com
Subject: Re: [musl] Hung processes with althttpd web server
Date: Thu, 5 Oct 2023 15:39:26 +0200	[thread overview]
Message-ID: <20231005133926.GC1427497@port70.net> (raw)
In-Reply-To: <CAGP1gyM6P76mrJyXuLrdfCswGdtxrQZgPm2QY8xpU2ayzY_O-Q@mail.gmail.com>

* Carl Chave <online@chave.us> [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/ld-musl-x86_64.so.1
> #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

etc

  reply	other threads:[~2023-10-05 13:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05  1:41 Carl Chave
2023-10-05  2:15 ` Rich Felker
2023-10-05  2:43   ` Carl Chave
2023-10-05 13:39     ` Szabolcs Nagy [this message]
2023-10-05 18:26       ` Carl Chave
2023-10-05 18:48         ` Markus Wichmann
2023-10-05 19:06           ` Carl Chave
2023-10-05  3:37 ` Markus Wichmann
2023-10-05 12:39   ` Rich Felker
2023-10-05 18:34     ` Markus Wichmann
2023-10-05 18:52   ` Carl Chave

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231005133926.GC1427497@port70.net \
    --to=nsz@port70.net \
    --cc=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    --cc=online@chave.us \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).