emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gtk3, emacs 24 and gnome shell


From: Michael Welsh Duggan
Subject: Re: gtk3, emacs 24 and gnome shell
Date: Sat, 29 Oct 2011 11:45:47 -0400
User-agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.90 (gnu/linux)

Eli Zaretskii <address@hidden> writes:

>> From: Michael Welsh Duggan <address@hidden>
>> Date: Fri, 28 Oct 2011 19:30:03 -0400
>> Cc: Tassilo Horn <address@hidden>, address@hidden
>> 
>> 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
(address@hidden)



reply via email to

[Prev in Thread] Current Thread [Next in Thread]