* bug#19432: backtrace for errors that occur inside process sentinels
@ 2014-12-22 19:43 Jonas Bernoulli
2014-12-23 4:15 ` Stefan Monnier
0 siblings, 1 reply; 4+ messages in thread
From: Jonas Bernoulli @ 2014-12-22 19:43 UTC (permalink / raw)
To: 19432
Please provide a way to get backtraces for errors that occur inside
process sentinels. Something similar to `toggle-debug-on-error', I
suppose.
This is a late follow up to
http://emacs.stackexchange.com/questions/3552/how-to-debug-errors-in-sentinels-and-during-font-lock
Thanks,
Jonas
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#19432: backtrace for errors that occur inside process sentinels
2014-12-22 19:43 bug#19432: backtrace for errors that occur inside process sentinels Jonas Bernoulli
@ 2014-12-23 4:15 ` Stefan Monnier
2015-12-26 16:34 ` Lars Ingebrigtsen
0 siblings, 1 reply; 4+ messages in thread
From: Stefan Monnier @ 2014-12-23 4:15 UTC (permalink / raw)
To: Jonas Bernoulli; +Cc: 19432
> Please provide a way to get backtraces for errors that occur inside
> process sentinels.
(setq debug-on-error t) works for me:
emacs -Q --eval '(setq debug-on-error t)' \
--eval '(let ((proc (start-process "foo" nil "true"))) \
(set-process-sentinel proc (lambda (&rest args) \
(+ args 2))))'
brings up a *Backtrace* buffer just fine.
Stefan
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#19432: backtrace for errors that occur inside process sentinels
2014-12-23 4:15 ` Stefan Monnier
@ 2015-12-26 16:34 ` Lars Ingebrigtsen
2016-02-29 5:47 ` Lars Ingebrigtsen
0 siblings, 1 reply; 4+ messages in thread
From: Lars Ingebrigtsen @ 2015-12-26 16:34 UTC (permalink / raw)
To: Stefan Monnier; +Cc: 19432, Jonas Bernoulli
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Please provide a way to get backtraces for errors that occur inside
>> process sentinels.
>
> (setq debug-on-error t) works for me:
>
> emacs -Q --eval '(setq debug-on-error t)' \
> --eval '(let ((proc (start-process "foo" nil "true"))) \
> (set-process-sentinel proc (lambda (&rest args) \
> (+ args 2))))'
>
> brings up a *Backtrace* buffer just fine.
So this doesn't seem reproducible. Jonas, do you have a recipe how to
trigger this bug?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#19432: backtrace for errors that occur inside process sentinels
2015-12-26 16:34 ` Lars Ingebrigtsen
@ 2016-02-29 5:47 ` Lars Ingebrigtsen
0 siblings, 0 replies; 4+ messages in thread
From: Lars Ingebrigtsen @ 2016-02-29 5:47 UTC (permalink / raw)
To: Stefan Monnier; +Cc: 19432, Jonas Bernoulli
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>> Please provide a way to get backtraces for errors that occur inside
>>> process sentinels.
>>
>> (setq debug-on-error t) works for me:
>>
>> emacs -Q --eval '(setq debug-on-error t)' \
>> --eval '(let ((proc (start-process "foo" nil "true"))) \
>> (set-process-sentinel proc (lambda (&rest args) \
>> (+ args 2))))'
>>
>> brings up a *Backtrace* buffer just fine.
>
> So this doesn't seem reproducible. Jonas, do you have a recipe how to
> trigger this bug?
More information was requested, but no response was given within a few
months, so I'm closing this bug report. If the problem still exists,
please reopen this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-02-29 5:47 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-12-22 19:43 bug#19432: backtrace for errors that occur inside process sentinels Jonas Bernoulli
2014-12-23 4:15 ` Stefan Monnier
2015-12-26 16:34 ` Lars Ingebrigtsen
2016-02-29 5:47 ` Lars Ingebrigtsen
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).