From: Tom Tromey <tom@tromey.com>
To: Zeck S <zeck654321@gmail.com>
Cc: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [RFC][PATCH?] fixed some segfaults and bugs in mdebug support
Date: Fri, 15 Dec 2023 12:26:34 -0700 [thread overview]
Message-ID: <87edfn6zdh.fsf@tromey.com> (raw)
In-Reply-To: <CAMeZSLCeShz2q_uW4RMMJQ5304AQZP7ogWUmkbPvaYqg++zTYg@mail.gmail.com> (Zeck S.'s message of "Mon, 11 Dec 2023 08:48:54 -0600")
>>>>> "Zeck" == Zeck S <zeck654321@gmail.com> writes:
Zeck> And it has been very useful, but legitimately some of the tests
Zeck> just can't pass (or sometimes even build) with this nasty old
Zeck> compiler and symbol format combination.
Depending on how much work you want to do on this, it's also possible to
arrange for tests to be skipped for your target. E.g., many of the
gdb.dwarf2 tests start with:
require dwarf2_support
dwarf2_support is just a proc in lib/dwarf.exp... if it returns 0, this
entire test will be skipped on your target.
Possibly some tests are missing some 'require' line. And if your
compiler is old enough, probably a lot of C++ tests and the like will
either not compile or will generate unusable debuginfo. These could be
patched to depend on a compiler or C++ version perhaps.
Tom
next prev parent reply other threads:[~2023-12-15 19:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 8:13 Zeck S
2023-10-23 9:40 ` Andrew Burgess
2023-10-24 0:25 ` Zeck S
2023-11-11 3:07 ` Zeck S
2023-12-04 3:36 ` Zeck S
2023-12-11 11:42 ` Zeck S
2023-12-11 14:03 ` Andrew Burgess
2023-12-11 14:48 ` Zeck S
2023-12-15 19:26 ` Tom Tromey [this message]
2023-12-18 15:50 ` Andrew Burgess
2023-12-25 5:42 ` Zeck S
2024-02-07 13:33 ` [PATCH] mdebug fix Zeck S
2024-02-16 2:45 ` [RFC][PATCH?] fixed some segfaults and bugs in mdebug support Zeck S
2024-03-13 2:09 ` Zeck S
2023-12-15 19:27 ` Tom Tromey
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=87edfn6zdh.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=zeck654321@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.
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).