[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Executing Emacs commands when a gdb breakpoint is hit
From: |
Eli Zaretskii |
Subject: |
Re: Executing Emacs commands when a gdb breakpoint is hit |
Date: |
Wed, 22 Jan 2020 19:04:41 +0200 |
> From: Skip Montanaro <skip.montanaro@gmail.com>
> Date: Wed, 22 Jan 2020 07:48:17 -0600
> Cc: Help GNU Emacs <help-gnu-emacs@gnu.org>
>
> Now, is it possible to trigger an Emacs Lisp function of some sort when a GDB
> breakpoint is hit? I see the gdb-stopped-functions variable. This simple
> function seems to execute when my
> compiler_set_lineno breakpoint is hit:
>
> (defun stopped (reason)
> (message "%s" reason))
>
> (setq gdb-stopped-functions '(stopped))
So you already have the answer to that question: gdb-stopped-functions.
> I tried sticking in a short sleep, but that didn't help. Is there a way to
> force the *gud-python* to be ready for
> user input before calling get-gdb-value?
I don't think I understand what you are trying to do and what are the
difficulties, sorry.
- Executing Emacs commands when a gdb breakpoint is hit, Skip Montanaro, 2020/01/21
- Re: Executing Emacs commands when a gdb breakpoint is hit, Eli Zaretskii, 2020/01/21
- Re: Executing Emacs commands when a gdb breakpoint is hit, Skip Montanaro, 2020/01/22
- Re: Executing Emacs commands when a gdb breakpoint is hit,
Eli Zaretskii <=
- Re: Executing Emacs commands when a gdb breakpoint is hit, otadmor ., 2020/01/22
- Re: Executing Emacs commands when a gdb breakpoint is hit, Skip Montanaro, 2020/01/22
- Re: Executing Emacs commands when a gdb breakpoint is hit, Eli Zaretskii, 2020/01/23
- Re: Executing Emacs commands when a gdb breakpoint is hit, Skip Montanaro, 2020/01/23
- Re: Executing Emacs commands when a gdb breakpoint is hit, Eli Zaretskii, 2020/01/24