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
