From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Debug Fortran 90 code in Emacs with arguments.
Date: Wed, 06 Apr 2022 17:12:35 +0300 [thread overview]
Message-ID: <83h776cncc.fsf@gnu.org> (raw)
In-Reply-To: <CAGP6POK3FCsiTH2O=XCWFZSHd63JAUcyzMi13wAF68xxjeqmZQ@mail.gmail.com> (message from Hongyi Zhao on Wed, 6 Apr 2022 21:05:24 +0800)
> From: Hongyi Zhao <hongyi.zhao@gmail.com>
> Date: Wed, 6 Apr 2022 21:05:24 +0800
> Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
>
> On Wed, Apr 6, 2022 at 6:51 PM Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > > Set a breakpoint by going to the source line of the program you're
> > > debugging, and typing:
> > >
> > > C-x [space]
> > >
> > > (That's the space bar.) GDB will tell you that you've just set a breakpoint.
> >
> > That description is outdated, please report a bug to the GDB
> > developers.
>
> The above description is written before many years (fall 1997), and
> the author may not bet GDB developers. So, why do you give the above
> suggestion?
Because most of it is still valid for first-time GDB users, and the
GDB manual is not supposed to be the canonical source of information
about Emacs, anyway.
next prev parent reply other threads:[~2022-04-06 14:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 2:27 Debug Fortran 90 code in Emacs with arguments Hongyi Zhao
2022-04-05 11:18 ` Eli Zaretskii
2022-04-05 12:57 ` Hongyi Zhao
2022-04-05 13:00 ` Hongyi Zhao
2022-04-05 13:19 ` Eli Zaretskii
2022-04-05 13:23 ` Eli Zaretskii
2022-04-05 13:52 ` Hongyi Zhao
2022-04-05 14:02 ` Eli Zaretskii
2022-04-05 14:14 ` Hongyi Zhao
2022-04-05 14:19 ` Hongyi Zhao
2022-04-05 15:52 ` Eli Zaretskii
2022-04-06 1:46 ` Hongyi Zhao
2022-04-06 2:32 ` Eli Zaretskii
2022-04-06 3:02 ` Hongyi Zhao
2022-04-06 2:26 ` Hongyi Zhao
2022-04-06 10:50 ` Eli Zaretskii
2022-04-06 13:05 ` Hongyi Zhao
2022-04-06 14:12 ` Eli Zaretskii [this message]
2022-04-06 14:42 ` Hongyi Zhao
2022-04-06 15:42 ` Eli Zaretskii
2022-04-07 2:02 ` Hongyi Zhao
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=83h776cncc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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.