public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mjw@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: [PATCH] Add --core-pattern option to eu-stack
Date: Fri, 28 Nov 2014 15:44:44 +0100	[thread overview]
Message-ID: <1417185884.4954.55.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: 20141127214130.GA29584@host2.jankratochvil.net

[-- Attachment #1: Type: text/plain, Size: 1597 bytes --]

On Thu, 2014-11-27 at 22:41 +0100, Jan Kratochvil wrote:
> I just find it improbable one would not need a single other kind of
> information than what eu-stack can provide.

FWIW I found it useful. All other core_pattern programs I have seen seem
somewhat bloated and I normally deinstall them. It is nice to have a
small light-weight and quick core_pattern filter that just dumps the
exiting/crashing backtrace in a file and does nothing else. IMHO.

I don't think any distro would install it as standard core_pattern
filter, they probably go with abrt or systemd-coredump to get all the
fancy output. But for a hacker box it seems a nice thing to have around.

> > 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

So the missing functionality really is just redirecting the output (and
stderr)? What is in elfutils-boot?

BTW I was just using:
/usr/bin/eu-stack --core-pattern -v --p %i -o /proc/%p/cwd/%i.stack
without any shell wrapper.

Cheers,

Mark

             reply	other threads:[~2014-11-28 14:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-28 14:44 Mark Wielaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-11-28 15:04 Mark Wielaard
2014-11-28 14:27 Mark Wielaard
2014-11-27 21:47 Jan Kratochvil
2014-11-27 21:41 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=1417185884.4954.55.camel@bordewijk.wildebeest.org \
    --to=mjw@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).