* [ruby-core:72842] [Ruby trunk - Feature #11987] [Open] daemons can't show the backtrace of rb_bug
[not found] <redmine.issue-11987.20160113103857@ruby-lang.org>
@ 2016-01-13 10:38 ` naruse
2016-01-13 10:49 ` [ruby-core:72843] " Eric Wong
0 siblings, 1 reply; 2+ messages in thread
From: naruse @ 2016-01-13 10:38 UTC (permalink / raw
To: ruby-core
Issue #11987 has been reported by Yui NARUSE.
----------------------------------------
Feature #11987: daemons can't show the backtrace of rb_bug
https://bugs.ruby-lang.org/issues/11987
* Author: Yui NARUSE
* Status: Open
* Priority: Normal
* Assignee:
----------------------------------------
Ruby shows backtrace and other information into stderr on rb_bug.
But daemon process redirects stderr into /dev/null.
How do I get the log?
NOTE: if I can reproduce this, I can use strace to get it. But issues are not always reproducible.
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
* [ruby-core:72843] Re: [Ruby trunk - Feature #11987] [Open] daemons can't show the backtrace of rb_bug
2016-01-13 10:38 ` [ruby-core:72842] [Ruby trunk - Feature #11987] [Open] daemons can't show the backtrace of rb_bug naruse
@ 2016-01-13 10:49 ` Eric Wong
0 siblings, 0 replies; 2+ messages in thread
From: Eric Wong @ 2016-01-13 10:49 UTC (permalink / raw
To: ruby-core
I always recommend pointing stderr to a regular file using
IO#reopen after daemonization. Perhaps kwargs may be added
to Process.daemon to encourage this usage?
Process.daemon err: '/path/to/stderr.log', out: '/path/to/stdout.log'
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-01-13 10:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <redmine.issue-11987.20160113103857@ruby-lang.org>
2016-01-13 10:38 ` [ruby-core:72842] [Ruby trunk - Feature #11987] [Open] daemons can't show the backtrace of rb_bug naruse
2016-01-13 10:49 ` [ruby-core:72843] " Eric Wong
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).