From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] Fu ....
Date: Tue, 10 May 2016 14:20:28 +0200 [thread overview]
Message-ID: <f5d738da31bac2f1536ad3eefe10a9b4@felloff.net> (raw)
In-Reply-To: <45cfa9048d25c7fa7ffc41d6a8f5bd3d@titan.jitaku.localdomain>
use snap(4) and make a process snapshot. then
try to make a stack trace in acid like:
term% acid <pid>
acid: lstk()
--
cinap
next prev parent reply other threads:[~2016-05-10 12:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 7:12 Fu kokamoto
2016-05-10 9:28 ` [9front] Fu Travis Moore
2016-05-10 10:39 ` kokamoto
2016-05-10 11:03 ` Travis Moore
2016-05-10 11:34 ` kokamoto
2016-05-10 11:36 ` kokamoto
2016-05-10 11:42 ` kokamoto
2016-05-10 12:20 ` cinap_lenrek [this message]
2016-05-10 12:30 ` kokamoto
2016-05-11 0:31 ` kokamoto
2016-05-11 0:42 ` stanley lieber
2016-05-12 0:35 ` kokamoto
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=f5d738da31bac2f1536ad3eefe10a9b4@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).