public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/29804] [gdb/tdep, vax] Remove gdbarch_deprecated_function_start_offset
Date: Sat, 19 Nov 2022 09:50:51 +0000 [thread overview]
Message-ID: <bug-29804-4717-EzOwpwL0P2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29804-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29804
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Maciej W. Rozycki from comment #5)
> My VAX box is up and running, however I note that we have no `gdbserver'
> for VAX/NetBSD and I have no TCL/Expect/DejaGNU installed there. Native
> testing would take forever anyway. Given that we do have NetBSD backends
> in `gdbserver' already perhaps it'll be the easiest if we add support to
> the VAX target there. I'll see what I can do, but it may take a while.
Thanks for looking into this.
A setup that might also work and doesn't require gdbserver is remote
host+target, which runs tcl/expect/dejagnu on a some local machine (build
role), and runs compiler, gdb and target execs on a remote machine (host/target
role). But I suppose it would run into the same "would take forever" problem
as native testing.
It all makes me wonder how this target used to be validated. Maybe done in a
time when the testsuite was smaller, and took significantly less time to
execute. Or perhaps a subset of the testsuite was taken and deemed sufficient.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-11-19 9:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 9:48 [Bug tdep/29804] New: " vries at gcc dot gnu.org
2022-11-18 9:55 ` [Bug tdep/29804] " vries at gcc dot gnu.org
2022-11-18 10:20 ` vries at gcc dot gnu.org
2022-11-18 15:55 ` tromey at sourceware dot org
2022-11-18 16:01 ` vries at gcc dot gnu.org
2022-11-18 20:13 ` macro at orcam dot me.uk
2022-11-19 9:50 ` vries at gcc dot gnu.org [this message]
2022-11-19 13:44 ` macro at orcam dot me.uk
2022-11-21 6:37 ` vries at gcc dot gnu.org
2022-11-22 15:58 ` macro at orcam dot me.uk
2022-12-06 16:25 ` tromey at sourceware dot org
2022-12-06 16:43 ` macro at orcam dot me.uk
2023-01-28 14:09 ` macro at orcam dot me.uk
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=bug-29804-4717-EzOwpwL0P2@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).