From: Eli Zaretskii <eliz@gnu.org>
To: gdb@sourceware.org
Subject: Re: Running selftests in GDB
Date: Mon, 28 Sep 2020 19:53:20 +0300 [thread overview]
Message-ID: <83pn65lu67.fsf@gnu.org> (raw)
In-Reply-To: <83h7rimej3.fsf@gnu.org> (message from Eli Zaretskii via Gdb on Mon, 28 Sep 2020 12:33:36 +0300)
> Date: Mon, 28 Sep 2020 12:33:36 +0300
> From: Eli Zaretskii via Gdb <gdb@sourceware.org>
>
> By default, GDB built from a release tarball doesn't include the
> selftest. I've configured GDB with --enable-unit-tests, and then some
> selftests are available. But not all: a development version runs 63
> unit tests, whereas the release version configured with unit tests
> runs only 24.
>
> How do I enable all the selftests that are available in the
> development build?
Answering myself: after reconfiguring with --enable-unit-tests, one
should make sure gdb/init.c is regenerated. It looks like it won't be
regenerated, unless you touch one of the source files mentioned in
COMMON_SFILES by gdb/Makefile.
next prev parent reply other threads:[~2020-09-28 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 9:33 Eli Zaretskii
2020-09-28 16:53 ` Eli Zaretskii [this message]
2020-10-04 15:52 ` Maciej W. Rozycki
2020-10-04 16:18 ` Eli Zaretskii
2020-10-04 17:56 ` Maciej W. Rozycki
2020-10-04 18:27 ` 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=83pn65lu67.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.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.
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).