From: Eli Zaretskii <eliz@gnu.org>
To: Wilhelm Kirschbaum <wkirschbaum@gmail.com>
Cc: 49864@debbugs.gnu.org
Subject: bug#49864: 28.0.50; Fails to start after "make install"
Date: Thu, 05 Aug 2021 10:58:56 +0300 [thread overview]
Message-ID: <83mtpwjpa7.fsf@gnu.org> (raw)
In-Reply-To: <CAOS0-35QXD=SD+2F47Z=pcrOsNh10tmEDJ58NcnDf2GB29Y7yg@mail.gmail.com> (message from Wilhelm Kirschbaum on Thu, 5 Aug 2021 09:14:10 +0200)
> From: Wilhelm Kirschbaum <wkirschbaum@gmail.com>
> Date: Thu, 5 Aug 2021 09:14:10 +0200
> Cc: 49864@debbugs.gnu.org
>
> Yes, of course, but I will only be able to do it a bit later today. I am not too familiar with GDB though.
Thanks. The instructions are below:
$ cd /home/wilhelm/src/tools/emacs/src
$ gdb /usr/local/bin/emacs-28.0.50
...
(gdb) source ./.gdbinit
(gdb) break pdumper.c:5315
(gdb) r -Q
When GDB announces that the breakpoint at pdumper.c:5315 breaks, do
this:
(gdb) p cu_file1
(gdb) xstring
(gdb) p cu_file2
(gdb) xstring
and show the results of these commands. Then step through the code,
one line at a time, with the "n" ("next") command. Eventually, you
should get to line 5321:
5321 if (file_access_p (fndata, F_OK))
Then show the value of fndata, which should be a file name:
(gdb) p fndata
Type "next" again. If the file_access_p call fails (returns 'false'),
show the value of errno immediately after stepping past the line that
calls file_access_p:
(gdb) p errno
In that case (if file_access_p fails), the "next" command will land
you in this block:
else
{
eln_fname = make_uninit_string (execdir_len + fn2_len);
fndata = SSDATA (eln_fname);
memcpy (fndata, emacs_execdir, execdir_len);
memcpy (fndata + execdir_len, SSDATA (cu_file2), fn2_len);
installation_state = LOCAL_BUILD;
}
Please type "n" ("next") repeatedly until you get to the last line,
which starts with "installation_state =", and show the value of
fndata:
(gdb) p fndata
Finally, keep stepping with "n" until you come to this line:
comp_u->handle = dynlib_open (SSDATA (eln_fname));
and type the following commands:
(gdb) p eln_fname
(gdb) xstring
and show their results.
You can then terminate the GDB session:
(gdb) q
(Answer "y" if it asks whether to quit.)
I hope the data you collect and report will explain what happens, or
at least give us a direction in which to look for the explanation.
Thanks again for your help in this matter.
next prev parent reply other threads:[~2021-08-05 7:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 5:42 bug#49864: 28.0.50; Fails to start after "make install" Wilhelm Kirschbaum
2021-08-04 11:56 ` Eli Zaretskii
2021-08-05 6:42 ` Wilhelm Kirschbaum
2021-08-05 6:50 ` Eli Zaretskii
2021-08-05 7:02 ` Wilhelm Kirschbaum
2021-08-05 7:09 ` Eli Zaretskii
2021-08-05 7:14 ` Wilhelm Kirschbaum
2021-08-05 7:58 ` Eli Zaretskii [this message]
2021-08-05 12:44 ` Wilhelm Kirschbaum
2021-08-05 13:33 ` Eli Zaretskii
2021-08-05 14:04 ` Eli Zaretskii
2021-08-05 15:21 ` Wilhelm Kirschbaum
2021-08-05 16:29 ` Eli Zaretskii
2021-08-05 18:27 ` Wilhelm Kirschbaum
2021-08-06 6:48 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mtpwjpa7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=49864@debbugs.gnu.org \
--cc=wkirschbaum@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.