From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 71292@debbugs.gnu.org
Subject: bug#71292: 30.0.50; macOS: .elns have no debug info
Date: Fri, 31 May 2024 21:32:23 +0300 [thread overview]
Message-ID: <86a5k5q1c8.fsf@gnu.org> (raw)
In-Reply-To: <m2bk4ln942.fsf@pro2.fritz.box> (message from Gerd Möllmann on Fri, 31 May 2024 20:12:45 +0200)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: 71292@debbugs.gnu.org
> Date: Fri, 31 May 2024 20:12:45 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Then how about using -keep-temps as part of native-comp-debug = 3?
>
> I think you mean debug >= 2?
Mo, I meant > 2.
> Anyway, debug info is also valuable when you don't have the C file, in
> the disassembly. That is for debug > 0. Otherwise you see only bare hex
> addresses and such.
Debug info and keeping the *.o files is not the same. Keeping the *.o
files is really gross, which is why I suggested debug > 2 (as it keeps
other intermediate files).
Doesn't macOS support separate debug info, which can be created with
objcopy? If it does, you could copy the debug info from the *.o
files, and then deleting them would not hamper debugging.
next prev parent reply other threads:[~2024-05-31 18:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 13:55 bug#71292: 30.0.50; macOS: .elns have no debug info Gerd Möllmann
2024-05-31 15:39 ` Eli Zaretskii
2024-05-31 16:31 ` Gerd Möllmann
2024-05-31 18:07 ` Eli Zaretskii
2024-05-31 18:12 ` Gerd Möllmann
2024-05-31 18:32 ` Eli Zaretskii [this message]
2024-05-31 18:52 ` Gerd Möllmann
2024-05-31 19:05 ` Eli Zaretskii
2024-05-31 19:22 ` Gerd Möllmann
2024-06-01 6:15 ` Gerd Möllmann
2024-06-01 6:24 ` Gerd Möllmann
2024-06-01 6:36 ` Eli Zaretskii
2024-06-02 5:41 ` Gerd Möllmann
2024-06-02 6:40 ` Eli Zaretskii
2024-06-03 15:30 ` Andrea Corallo
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=86a5k5q1c8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71292@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.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 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.