unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 71292@debbugs.gnu.org
Subject: bug#71292: 30.0.50; macOS: .elns have no debug info
Date: Fri, 31 May 2024 20:12:45 +0200	[thread overview]
Message-ID: <m2bk4ln942.fsf@pro2.fritz.box> (raw)
In-Reply-To: <86frtxq2ih.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 31 May 2024 21:07:02 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Cc: 71292@debbugs.gnu.org
>> Date: Fri, 31 May 2024 18:31:35 +0200
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> >> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> >> Date: Fri, 31 May 2024 15:55:43 +0200
>> >> 
>> >> Example in LLDB with native-comp-debug == 2
>> >> 
>> >>   frame #7: 0x000000010350db68 comp-7672a6ed-3a3b5dd7.eln`F636f6d702d2d6c696d706c6966792d626c6f636b_comp__limplify_block_0 + 1632 at comp-7672a6ed-3a3b5dd7.c:101440
>> >> 
>> >> and one can look at the C file.
>> >
>> > But the C file is also generally unavailable, and not only on macOS.
>> 
>> The C file is generated by libgccjit when setting native-comp-debug to 2.
>
> Then how about using -keep-temps as part of native-comp-debug = 3?

I think you mean debug >= 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.





  reply	other threads:[~2024-05-31 18:12 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 [this message]
2024-05-31 18:32         ` Eli Zaretskii
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

  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=m2bk4ln942.fsf@pro2.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=71292@debbugs.gnu.org \
    --cc=eliz@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 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).