From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Nikishkin <lockywolf@gmail.com>
Cc: 40271@debbugs.gnu.org
Subject: bug#40271: 26.3; gdb-mode fails to initialize if the target executable is built without symbols
Date: Sat, 28 Mar 2020 16:53:20 +0300 [thread overview]
Message-ID: <83blog7fhr.fsf@gnu.org> (raw)
In-Reply-To: <CA+A2iZZ-mPD3CmOz2CkN1V4ZC-pjabRmWEpu51-9WVuJeeY=4w@mail.gmail.com> (message from Vladimir Nikishkin on Sat, 28 Mar 2020 21:26:12 +0800)
> From: Vladimir Nikishkin <lockywolf@gmail.com>
> Date: Sat, 28 Mar 2020 21:26:12 +0800
> Cc: 40271@debbugs.gnu.org
>
> (gdb)
> -file-list-exec-source-file
> ^done,line="1",file="../sysdeps/x86_64/start.S",fullname="/root/glibc-2a0c65c5167af50893952729ba38cc68/glibc-2.30/csu/../sysdeps/x86_64/start.S",macro-info="0"
> (gdb)
>
> I am confused, because libc is also expected to be stripped. Is this a gdb bug?
I don't think so. start.S is probably the startup module that gets
linked into every program; it is provided by glibc. I don't know
enough about linking on GNU/Linux, but I think if you strip the
binary, this file name will also be stripped, and everything will work
again (except that you will be unable to step through the source).
> Frankly speaking, I just found this by mistake. I forgot to issue
> -ggdb when compiling my code. I'm not a reverse engineer.
Right, that figures. So I'm unsure we should do anything about this
in Emacs. Though maybe we could have a special test for a source file
called "start.S".
next prev parent reply other threads:[~2020-03-28 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 11:51 bug#40271: 26.3; gdb-mode fails to initialize if the target executable is built without symbols Vladimir Nikishkin
2020-03-28 12:11 ` Eli Zaretskii
2020-03-28 12:30 ` Eli Zaretskii
[not found] ` <CA+A2iZYfyhxWyJmNdGVm-4rxhVGXZD3zCU3kvCzU7uynxXxKQQ@mail.gmail.com>
2020-03-28 12:39 ` bug#40271: Fwd: " Vladimir Nikishkin
2020-03-28 13:12 ` Eli Zaretskii
2020-03-28 13:26 ` Vladimir Nikishkin
2020-03-28 13:27 ` Vladimir Nikishkin
2020-03-28 13:53 ` Eli Zaretskii [this message]
2022-01-31 18:43 ` Lars Ingebrigtsen
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=83blog7fhr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40271@debbugs.gnu.org \
--cc=lockywolf@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.