unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 22:05:25 +0300	[thread overview]
Message-ID: <868qzppzt6.fsf@gnu.org> (raw)
In-Reply-To: <m27cf9n7a7.fsf@pro2.fritz.box> (message from Gerd Möllmann on Fri, 31 May 2024 20:52:16 +0200)

> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: 71292@debbugs.gnu.org
> Date: Fri, 31 May 2024 20:52:16 +0200
> 
> > 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.
> 
> MacOS has .dSYM bundles, but how would you convince libgccjit/gcc to
> invoke dsymutil to produce them before it deletes the .o files? I don't
> see how that can be done.

So let me be sure I understand: there's no was on macOS to produce a
shared library with debug info, except by keeping the *.o files
around?  IOW, when the linker produces a shared library, it doesn't
copy the debug info from the *.o files to the shared library, not even
given some optional command-line switch?





  reply	other threads:[~2024-05-31 19:05 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
2024-05-31 18:52           ` Gerd Möllmann
2024-05-31 19:05             ` Eli Zaretskii [this message]
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

  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=868qzppzt6.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 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).