public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel@rtems.org>
To: Eli Zaretskii via Gdb <gdb@sourceware.org>
Subject: mips jmr3904 simulator broken
Date: Mon, 1 Aug 2022 14:58:44 -0500	[thread overview]
Message-ID: <CAF9ehCU9Dg+LbpzekYYxtfyT4+Rm-WcCT1EEKLGvmAGc7C_YVQ@mail.gmail.com> (raw)

Hi

RTEMS has a board support package for the jmr3904 simulator in gdb and it
has broken.   I used git bisect to track down when this broke. This is a
portion of the git bisect log

good  gdb-10.2-release
bad   gdb-11.2-release
...............
git bisect good 162c6aef1f3a96923e75f0b4ef430822d273465c
# good: [07490bf81d2fc91676eb71b77e07f80f20fc1b54] sim: unify various
library testing logic
git bisect good 07490bf81d2fc91676eb71b77e07f80f20fc1b54
# bad: [ce3ec98acd2f344ae911de3f41dd2e3c6c68b141] sim: unify gettext/intl
probing logic
git bisect bad ce3ec98acd2f344ae911de3f41dd2e3c6c68b141
# good: [c30420d82a0b743285cf8333f90ca85274632714] elf: Update
GNU_PROPERTY_UINT32_[AND|OR]_XXX tests
git bisect good c30420d82a0b743285cf8333f90ca85274632714
# bad: [bc56166f66244a9e3abc62c7bc595a6f800f23b0] sim: unify toolchain
dependency logic
git bisect bad bc56166f66244a9e3abc62c7bc595a6f800f23b0

The full bisect log, gdb output and a test executable are at
https://devel.rtems.org/ticket/4689. I was going to file this at the gdb
Bugzilla but am having an issue with my account right now.

Is there a test case for the jmr3904? Or is the RTEMS use case not
accounted for in a current test?

FWIW RTEMS stable tools for development use gdb 11.2 while the unstable are
tracking master.

Thanks.

--joel

             reply	other threads:[~2022-08-01 19:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 19:58 Joel Sherrill [this message]
2022-10-23 17:11 ` [PATCH] sim: mips/ppc/riscv: re-add AC_CANONICAL_SYSTEM [PR sim/29439] Mike Frysinger
2023-03-03 21:27   ` Jan-Benedict Glaw
2023-10-15 10:37     ` Mike Frysinger

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=CAF9ehCU9Dg+LbpzekYYxtfyT4+Rm-WcCT1EEKLGvmAGc7C_YVQ@mail.gmail.com \
    --to=joel@rtems.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).