From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] vac crash in libthread threadexitsall()
Date: Sun, 14 Feb 2021 15:43:06 +0100 [thread overview]
Message-ID: <91D3FF1D1C092D773820E38BA6D98CEF@felloff.net> (raw)
In-Reply-To: <d849fd69-c77d-46b4-914b-d56e484effff@www.fastmail.com>
you need to take a look at the memory image.
obviously, p is nil or garbage (you havnet told us the address
it faults on), but this should not happen.
it is most likely that a memory corruption has broken the
Proc* structures or at least the next pointer in one
of the proc's or the global _threadpq.
is there a way to reproduce it?
maybe you can make a memory snapshot if the process with
snap(4) when it happens again.
--
cinap
next prev parent reply other threads:[~2021-02-14 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 12:21 james palmer
2021-02-14 14:43 ` cinap_lenrek [this message]
2021-02-14 15:29 ` james palmer
2021-02-14 16:06 ` Noam Preil
2021-02-22 1:25 ` james palmer
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=91D3FF1D1C092D773820E38BA6D98CEF@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.org \
/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.
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).