From: Eli Zaretskii <eliz@gnu.org>
To: Bhavin Gandhi <bhavin7392@gmail.com>
Cc: 52376@debbugs.gnu.org, akrl@sdf.org
Subject: bug#52376: 28.0.90; libdir is missing from native-comp-eln-load-path with GTK3 build
Date: Fri, 10 Dec 2021 14:20:45 +0200 [thread overview]
Message-ID: <83pmq4slb6.fsf@gnu.org> (raw)
In-Reply-To: <CAOn=hbc5TK4_oBdjR6bowZpa3bp34x_Ncsg9QCGqG9mwQr9xDw@mail.gmail.com> (message from Bhavin Gandhi on Fri, 10 Dec 2021 17:21:58 +0530)
> From: Bhavin Gandhi <bhavin7392@gmail.com>
> Date: Fri, 10 Dec 2021 17:21:58 +0530
> Cc: akrl@sdf.org, 52376@debbugs.gnu.org
>
> On Fri, 10 Dec 2021 at 17:06, Eli Zaretskii <eliz@gnu.org> wrote:
> > Which breakpoint didn't break? the one at line 5321? That's because
> > the line number was incorrect, I think. Please set the breakpoint at
> > line 5319 instead, and then show us the results from the problematic
> > build.
>
> The one at 5319 didn't break.
Does _any_ line of code under RELOC_NATIVE_COMP_UNIT case get
executed? What if you set the breakpoint here:
#ifdef HAVE_NATIVE_COMP
case RELOC_NATIVE_COMP_UNIT:
{
static enum { UNKNOWN, LOCAL_BUILD, INSTALLED } installation_state;
struct Lisp_Native_Comp_Unit *comp_u = <<<<<<<<<<<<<<<<<<<<<<<
dump_ptr (dump_base, reloc_offset);
comp_u->lambda_gc_guard_h = CALLN (Fmake_hash_table, QCtest, Qeq);
(that's line number 5291), or on the next line, does that breakpoint
break? If it does, please step through the code and tell what gets
executed and why.
next prev parent reply other threads:[~2021-12-10 12:20 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 17:21 bug#52376: 28.0.90; libdir is missing from native-comp-eln-load-path with GTK3 build Bhavin Gandhi
2021-12-08 17:33 ` Eli Zaretskii
2021-12-08 18:05 ` Bhavin Gandhi
2021-12-08 18:25 ` Eli Zaretskii
2021-12-08 19:19 ` Bhavin Gandhi
2021-12-08 20:11 ` Eli Zaretskii
2021-12-08 20:31 ` Bhavin Gandhi
2021-12-09 11:06 ` Andrea Corallo
2021-12-09 17:09 ` Bhavin Gandhi
2021-12-09 17:23 ` Andrea Corallo
2021-12-09 18:29 ` Bhavin Gandhi
2021-12-09 20:14 ` Andrea Corallo
2021-12-09 20:18 ` Andrea Corallo
2021-12-10 9:25 ` Bhavin Gandhi
2021-12-10 9:45 ` Andrea Corallo
2021-12-10 10:00 ` Bhavin Gandhi
2021-12-10 11:36 ` Eli Zaretskii
2021-12-10 11:51 ` Bhavin Gandhi
2021-12-10 12:20 ` Eli Zaretskii [this message]
2021-12-10 14:38 ` Bhavin Gandhi
2021-12-10 14:50 ` Eli Zaretskii
2021-12-10 15:08 ` Eli Zaretskii
2021-12-10 15:47 ` Bhavin Gandhi
2021-12-10 16:56 ` Eli Zaretskii
2021-12-10 19:53 ` Ken Brown
2021-12-11 12:49 ` Eli Zaretskii
2022-01-01 17:12 ` Bhavin Gandhi
2022-01-01 17:26 ` Ken Brown
2022-01-02 17:33 ` Bhavin Gandhi
2022-01-01 17:27 ` Eli Zaretskii
2022-01-01 19:04 ` Bhavin Gandhi
2022-01-01 19:19 ` Eli Zaretskii
2022-01-02 17:39 ` Bhavin Gandhi
2022-01-02 18:22 ` Eli Zaretskii
2022-01-04 18:17 ` Bhavin Gandhi
2022-01-04 20:07 ` Eli Zaretskii
2021-12-10 11:32 ` Eli Zaretskii
2021-12-09 18:39 ` 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=83pmq4slb6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=52376@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=bhavin7392@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).