[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Debugging Emacs
From: |
Phillip Lord |
Subject: |
Re: Debugging Emacs |
Date: |
Sat, 28 Nov 2015 19:39:38 +0000 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Eli Zaretskii <address@hidden> writes:
>> Yes, that was sort of the idea. Personally, I'd not be too worried about
>> repeating things. I realise that this adds to the maintainance burden,
>> but references to later sections make for harder reading.
>
> It is OK to say something simple in the preamble, and refer to later
> sections for more in-depth detail.
>
> But I will now stop writing comments to a text I didn't yet see, and
> let you work on it instead ;-)
It was at the bottom of the original email!
While I am mailing, I had one idea which might simplify debugging.
Currently, you need to break-point some function to get control to GDB
before you launch Emacs. Why not add a null function to Emacs core for
the purpose? Guaranteed never to be called from anywhere, does nothing,
and with a breakpoint could be added to .gdbinit. Then, after running
Emacs, "M-x break" would automatically pass control back to GDB without
any further set up.
Just a thought.
Phil
- Debugging Emacs, Phillip Lord, 2015/11/27
- Re: Debugging Emacs, Karl Fogel, 2015/11/27
- Re: Debugging Emacs, Eli Zaretskii, 2015/11/27
- Re: Debugging Emacs, Eli Zaretskii, 2015/11/27
- Re: Debugging Emacs, Phillip Lord, 2015/11/27
- Re: Debugging Emacs, Eli Zaretskii, 2015/11/28
- Re: Debugging Emacs,
Phillip Lord <=
- Re: Debugging Emacs, Eli Zaretskii, 2015/11/28
- Re: Debugging Emacs, Phillip Lord, 2015/11/28
- Re: Debugging Emacs, Stephen Leake, 2015/11/29
- Re: Debugging Emacs, Marcin Borkowski, 2015/11/29
- Re: Debugging Emacs, John Wiegley, 2015/11/29
- Re: Debugging Emacs, Phillip Lord, 2015/11/29
- Re: Debugging Emacs, Nicolas Richard, 2015/11/30
- Re: Debugging Emacs, Marcin Borkowski, 2015/11/28
- Re: Debugging Emacs, Eli Zaretskii, 2015/11/28