[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#63084: 30.0.50; gud: set breakpoint while program is running
From: |
Eli Zaretskii |
Subject: |
bug#63084: 30.0.50; gud: set breakpoint while program is running |
Date: |
Fri, 05 May 2023 08:53:42 +0300 |
Ping! Could you please answer my questions below? Knowing the
answers is necessary for investigating this issue.
Thanks.
> Cc: 63084@debbugs.gnu.org
> Date: Wed, 26 Apr 2023 12:44:29 +0300
> From: Eli Zaretskii <eliz@gnu.org>
>
> > From: TatriX <tatrics@gmail.com>
> > Date: Wed, 26 Apr 2023 10:48:53 +0200
> > Cc: 63084@debbugs.gnu.org
> >
> > Oh, sorry. I tried on a different machine, and realized one have to use
> > "run&".
> >
> > So, here's what I did:
> >
> > $ cat main.c
> > #include <stdio.h>
> > #include <unistd.h>
> >
> > int main(void) {
> > for (int i = 0; ; i++) {
> > printf("%d\n", i);
> > sleep(1);
> > }
> > }
> >
> > $ gcc -g -o break main.c
> > $ emacs -Q main.c
> > M-x gdb RET
> > # in *gud-break*, NOTE it's "run&"
> > (gdb) run&
> > # in main.c
> > (goto-line 6)
> > (gud-break 1) ; or C-x C-a C-b
> > # nothing happens
> > M-: (gud-call "break 6") RET
> > # breakpoint is set and process execution is paused on hitting that
> > breakpoint
>
> What is the value of gdb-running and of gdb-non-stop after you "run&"
> the program?
>
>
>
>
- bug#63084: 30.0.50; gud: set breakpoint while program is running, Eli Zaretskii, 2023/05/05
- bug#63084: 30.0.50; gud: set breakpoint while program is running,
Eli Zaretskii <=
- bug#63084: 30.0.50; gud: set breakpoint while program is running, TatriX, 2023/05/05
- bug#63084: 30.0.50; gud: set breakpoint while program is running, Eli Zaretskii, 2023/05/06
- bug#63084: 30.0.50; gud: set breakpoint while program is running, TatriX, 2023/05/27
- bug#63084: 30.0.50; gud: set breakpoint while program is running, Eli Zaretskii, 2023/05/28
- bug#63084: 30.0.50; gud: set breakpoint while program is running, TatriX, 2023/05/28
- bug#63084: 30.0.50; gud: set breakpoint while program is running, Eli Zaretskii, 2023/05/29