unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pip Cet via "Emacs development discussions." <emacs-devel@gnu.org>
To: emacs-devel@gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: scratch/igc cedb01b6c9c: ; * README-IGC: Fix typos and wording.
Date: Fri, 13 Dec 2024 12:42:03 +0000	[thread overview]
Message-ID: <87jzc3hi1e.fsf@protonmail.com> (raw)
In-Reply-To: <20241213121925.3D2EE7667E7@vcs3.savannah.gnu.org>

"Eli Zaretskii" <eliz@gnu.org> writes:

> branch: scratch/igc
> commit cedb01b6c9c68051e00426415e21a960fdc3de76
> Author: Eli Zaretskii <eliz@gnu.org>
> Commit: Eli Zaretskii <eliz@gnu.org>
>
>     ; * README-IGC: Fix typos and wording.

Thanks!

> -It's recommended to use the .gdbinit file in the src/ subdirectory,
> -which configures gdb not to stop in this situation.
> +part of its normal operation.  When running Emacs with MPS support in a
> +debugger such as GDB, it is important to take this into account, because
> +the debugger might stop when this signal is raised, and make it look
> +like Emacs segfaulted.

Can we lose that last half-sentence?  Emacs did segfault, it's just that
the segfault was expected, so this will only cause confusion.

> +If you use GDB, it's recommended to use the .gdbinit file in the src/
> +subdirectory, which configures GDB not to stop in this situation.
> +Starting GDB from the src directory will cause it automatically load and
> +read the file, subject to the "auto-load safe-path" setting;
> +alternatively, you can force GDB to read that file manually, after
> +starting the debugger:
> +
> +  (gdb) source /path/to/emacs-igc/src/.gdbinit

Can we shorten this to just

> +If you use GDB, it's recommended to use the .gdbinit file in the src/
> +subdirectory:
> +
> +  (gdb) source /path/to/emacs-igc/src/.gdbinit

? I think those few people who use gdb distributions which allow
auto-loading .gdbinit files will know they can skip this step (and if
they don't, no harm done). The text you pushed makes it sound like we're
advising people to change the auto-load safe-path setting to include the
current directory, and we definitely don't want to do that.

(I intentionally omitted the "If you use GDB" part: we don't want people
to use lldb on GNU/Linux systems, which will result in less useful bug
reports)

Pip




       reply	other threads:[~2024-12-13 12:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <173409236461.371361.12797265888488865943@vcs3.savannah.gnu.org>
     [not found] ` <20241213121925.3D2EE7667E7@vcs3.savannah.gnu.org>
2024-12-13 12:42   ` Pip Cet via Emacs development discussions. [this message]
2024-12-13 13:06     ` scratch/igc cedb01b6c9c: ; * README-IGC: Fix typos and wording Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87jzc3hi1e.fsf@protonmail.com \
    --to=emacs-devel@gnu.org \
    --cc=eliz@gnu.org \
    --cc=pipcet@protonmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).