Bug#666742: xineliboutput-sxfe: vdr-sxfe fails on looking big images with xineliboutput plugin
Tobias Grimm
tobias.grimm at e-tobi.net
Sun Apr 14 19:31:04 UTC 2013
On 14.04.2013 20:38, Eric Lavarde wrote:
> In the mean time, a (probably stupid) question: I am the opinion that I
> had already everything in place to create a core dump but I didn't get
> one. I might have missed something and I didn't search further because I
> then thought that vdr-sxfe was not meant to core dump, but now that you
> ask for it, most probably it's also that I need ENABLE_CORE_DUMPS=1 to be
> set in vdr-sxfe's environment.
> Is this correct, or do I miss more?
ENABLE_CORE_DUMPS=1 makes the vdr init script call "ulimit -c unlimited"
and passes the "--userdump" option to vdr (required when vdr is run as
root but switches to a different user with -u).
vdr-sxfe is a separate process - setting ulimit -c unlimited is all you
should do. I couldn't find a custom SIGSEGV handler in the code, so this
should work.
I've just tested this with a kill -11 and it seems to work - a core dump
is created.
Please note, that you might need to add "ulimit -c unlimited" to the
script that calls vdr-sxfe on your system. By default the core dump will
be created in the working directory from which vdr-sxfe gets started, so
you might need to do a e.g. a "cd /tmp" before staring vdr-sxfe to be sure
its a writable directory.
Tobias
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-vdr-dvb-devel/attachments/20130414/0bd2a096/attachment.pgp>
More information about the pkg-vdr-dvb-devel
mailing list