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: larsi@gnus.org, 57309@debbugs.gnu.org, akrl@sdf.org
Subject: bug#57309: 29.0.50; Build error "trying to dump non fixed-up eln file"
Date: Sun, 21 Aug 2022 15:08:27 +0200	[thread overview]
Message-ID: <m2pmgt68xg.fsf@Mini.fritz.box> (raw)
In-Reply-To: <83a67xdad5.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 21 Aug 2022 15:55:34 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Does LLDB have the equivalent of "info share" command?  If so, do you
> see window-0d1b8b93-274db3e2.eln in the list of loaded shared
> libraries after the above?

My cheat sheet says that's 'image list' in lldb.  And it's there

[317] 41B40204-1F2E-3149-984B-D3FB2ED81504 0x00000001029c0000 /Users/gerd/emacs/master2/native-lisp/29_0_50-2dce7c3a/preloaded/format-c5b23b0d-d01f10d8.eln 
[318] F6785E28-B011-365D-8962-17A45A7DE211 0x0000000102d04000 /Users/gerd/emacs/master2/native-lisp/29_0_50-2dce7c3a/preloaded/bindings-d30713c5-e2748f1c.eln 
[319] FDDCB191-1E84-340C-9CDD-F269DB68737F 0x0000000104920000 /Users/gerd/emacs/master2/native-lisp/29_0_50-2dce7c3a/preloaded/window-0d1b8b93-274db3e2.eln 
[320] 324D97E7-B153-30E2-9303-8F76E32A3ABC 0x0000000104888000 /Users/gerd/emacs/master2/native-lisp/29_0_50-2dce7c3a/preloaded/files-1e8937b2-ae59da5e.eln 
[321] C4D48829-21CC-3E26-9EFB-6E51B9CF3E1B 0x0000000102d20000 /Users/gerd/emacs/master2/native-lisp/29_0_50-2dce7c3a/preloaded/macroexp-2c3e1495-553e0f8f.eln 






  reply	other threads:[~2022-08-21 13:08 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-20 12:55 bug#57309: 29.0.50; Build error "trying to dump non fixed-up eln file" Gerd Möllmann
2022-08-20 13:07 ` Lars Ingebrigtsen
2022-08-20 13:12   ` Gerd Möllmann
2022-08-20 13:18   ` Lars Ingebrigtsen
2022-08-20 13:21     ` Gerd Möllmann
2022-08-20 13:26       ` Eli Zaretskii
2022-08-20 13:29         ` Lars Ingebrigtsen
2022-08-20 13:45           ` Eli Zaretskii
2022-08-21 11:55             ` Lars Ingebrigtsen
2022-08-20 13:27       ` Lars Ingebrigtsen
2022-08-20 13:37         ` Gerd Möllmann
2022-08-20 14:32           ` Gerd Möllmann
2022-08-20 15:08             ` Gerd Möllmann
2022-08-21  7:03               ` Gerd Möllmann
2022-08-21  8:50                 ` Gerd Möllmann
2022-08-21 10:13                   ` Eli Zaretskii
2022-08-21 10:45                     ` Gerd Möllmann
2022-08-21 10:58                       ` Eli Zaretskii
2022-08-22  8:43                         ` Andrea Corallo
2022-08-20 15:25             ` Eli Zaretskii
2022-08-21  6:39               ` Gerd Möllmann
2022-08-21  6:43                 ` Eli Zaretskii
2022-08-21  6:47                   ` Gerd Möllmann
2022-08-21  7:03                     ` Eli Zaretskii
2022-08-21  7:13                       ` Gerd Möllmann
2022-08-21 11:57           ` Lars Ingebrigtsen
2022-08-21 12:28             ` Gerd Möllmann
2022-08-21 12:36               ` Eli Zaretskii
2022-08-21 12:46                 ` Gerd Möllmann
2022-08-21 12:55                   ` Eli Zaretskii
2022-08-21 13:08                     ` Gerd Möllmann [this message]
2022-08-21 13:19                       ` Eli Zaretskii
2022-08-21 13:11                     ` Gerd Möllmann
2022-08-21 13:14                       ` Gerd Möllmann
2022-08-21 13:39                         ` Gerd Möllmann
2022-08-21 13:45                           ` Eli Zaretskii
2022-08-21 13:56                             ` Gerd Möllmann
2022-08-21 14:02                               ` Eli Zaretskii
2022-08-22  8:49                               ` Andrea Corallo
2022-08-22  8:56                                 ` Gerd Möllmann
2022-08-22  9:35                                   ` 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=m2pmgt68xg.fsf@Mini.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=57309@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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).