From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: [PATCH] Add --core-pattern option to eu-stack
Date: Thu, 27 Nov 2014 22:41:30 +0100 [thread overview]
Message-ID: <20141127214130.GA29584@host2.jankratochvil.net> (raw)
In-Reply-To: 1417086351.4954.40.camel@bordewijk.wildebeest.org
[-- Attachment #1: Type: text/plain, Size: 1692 bytes --]
On Thu, 27 Nov 2014 12:05:51 +0100, Mark Wielaard wrote:
> We have -o,--output support in other utilities.
Those are ld, strip and unstrip. That is not for text output but for the
resulting ELF files which is IMO a different case.
BTW I am not against it, I just find it redundant. If thiAny program could
have -o|--output but in UNIX it is solved by the more general shell '>'.
> But maybe it isn't
> useful in general and people will always use shell redirection?
Currently it uses fopen "wx" which requires unique filename for each crash
dump unwind. One could use %p in the filename but that is also not completely
unique. Besides that one should IMO provide more information from /proc/PID/
(like fd/ ) than just the backtrace eu-stack can provide. One is also
interested in /proc/PID/exe which is not obvious from -l or -m (at least for
PIEs); although one could possibly use %E for core_pattern.
I just find it improbable one would not need a single other kind of
information than what eu-stack can provide.
> But if --core-pattern isn't useful without other code, then we should
> include that code too.
Yes, there could be provided some "contrib"-like core dumping shell script.
> Could you post what you have?
Nothing interesting, only for debugging eu-stack --core-pattern, when you ask:
#! /bin/bash
exec >>/tmp/out 2>>/tmp/out
date --iso=seconds
echo "$*"
cd /home/jkratoch/redhat/elfutils
. /home/jkratoch/t/elfutils-boot
ldd ./src/stack
# It locks up as strace holds fd 0:
#strace -s200 -o /tmp/out.strace -q ./src/stack --core-pattern -1 --pid=$1
exec ./src/stack --core-pattern -1 -l -m --pid=$1
Jan
next reply other threads:[~2014-11-27 21:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 21:41 Jan Kratochvil [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-28 15:04 Mark Wielaard
2014-11-28 14:44 Mark Wielaard
2014-11-28 14:27 Mark Wielaard
2014-11-27 21:47 Jan Kratochvil
2014-11-27 21:27 Jan Kratochvil
2014-11-27 11:17 Mark Wielaard
2014-11-27 11:05 Mark Wielaard
2014-11-27 11:04 Mark Wielaard
2014-11-26 20:57 Oleg Nesterov
2014-11-26 20:26 Jan Kratochvil
2014-11-26 20:08 Oleg Nesterov
2014-11-26 14:47 Jan Kratochvil
2014-11-26 14:44 Jan Kratochvil
2014-11-26 14:32 Jan Kratochvil
2014-11-03 13:22 Mark Wielaard
2014-10-30 21:55 Mark Wielaard
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=20141127214130.GA29584@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=elfutils-devel@lists.fedorahosted.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 read-only IMAP folder(s) and NNTP newsgroup(s).