all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Welsh Duggan <md5i@md5i.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tassilo@member.fsf.org, rasmus@gmx.us, emacs-devel@gnu.org
Subject: Re: gtk3, emacs 24 and gnome shell
Date: Sat, 29 Oct 2011 11:45:47 -0400	[thread overview]
Message-ID: <87mxcjiyxg.fsf@maru.md5i.com> (raw)
In-Reply-To: <83bot09nyk.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 29 Oct 2011 10:55:15 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Michael Welsh Duggan <md5i@md5i.com>
>> Date: Fri, 28 Oct 2011 19:30:03 -0400
>> Cc: Tassilo Horn <tassilo@member.fsf.org>, emacs-devel@gnu.org
>> 
>> In order to debug when running as a daemon, you need to add something
>> like the following to your src/.gdbinit file:
>> 
>> # Follow emacs when running using --daemon.  We need to follow the
>> # child of the daemonizing fork, and go back to following parents
>> # shortly afterward.
>> break main
>> commands
>>   silent
>>   set follow-fork-mode child
>>   continue
>> end
>> break init_signals
>> commands
>>   silent
>>   set follow-fork-mode parent
>>   continue
>> end
>
> This should be a good addition to etc/DEBUG.  However, I wonder:
>
>   . would "tbreak" be a better choice?

I used tbreak first, but was irritated when I tried to re-run emacs from
the debugger and 

>   . why do you need to put a breakpoint with identical commands in two
>     different functions? isn't the code path of becoming a daemon
>     deterministic enough to have it only in `main'?

The commands are not identical.  The first one sets follow-fork-mode to
child in order to follow emacs while it daemonizes itself, and the
second one sets it back to parent so that after daemonizing, we stay in
emacs whenever emacs forks and execs other processes.

-- 
Michael Welsh Duggan
(md5i@md5i.com)



  reply	other threads:[~2011-10-29 15:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24 12:06 gtk3, emacs 24 and gnome shell Andrea Crotti
2011-10-24 13:51 ` Tassilo Horn
2011-10-24 14:23   ` Andrea Crotti
2011-10-24 15:34     ` Tassilo Horn
2011-10-24 23:19 ` Rasmus
2011-10-25  4:30   ` Chong Yidong
2011-10-25  7:06   ` Tassilo Horn
2011-10-25  8:23     ` Rasmus
2011-10-25  8:52       ` Tassilo Horn
2011-10-27 20:46         ` Rasmus
2011-10-27 22:01           ` Paul Eggert
2011-10-27 22:42             ` bug#9893: " Paul Eggert
2011-10-28 21:02               ` Jan Djärv
2011-10-30 17:26               ` Jan Djärv
2011-10-31 20:13                 ` Paul Eggert
2011-10-27 22:01           ` Paul Eggert
2011-10-28  6:18           ` Tassilo Horn
2011-10-28  6:58             ` Eli Zaretskii
2011-10-28 18:21             ` Rasmus Pank Roulund
2011-10-28 23:30               ` Michael Welsh Duggan
2011-10-29  8:55                 ` Eli Zaretskii
2011-10-29 15:45                   ` Michael Welsh Duggan [this message]
2011-10-29 15:54                     ` Michael Welsh Duggan
2011-11-03  4:42                       ` Chris Moore
2011-11-03  1:08                 ` Rasmus
2011-11-03  3:59                   ` Eli Zaretskii
2011-11-04  1:02                     ` Rasmus
2011-11-03  1:08                 ` Rasmus
  -- strict thread matches above, loose matches on Subject: below --
2011-12-13 21:00 Benjamin Redelings
2011-12-14  7:07 ` Jan D.

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=87mxcjiyxg.fsf@maru.md5i.com \
    --to=md5i@md5i.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rasmus@gmx.us \
    --cc=tassilo@member.fsf.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.