mips jmr3904 simulator broken
Joel Sherrill <[email protected]>
| Newsgroups | gmane.comp.gdb.devel |
|---|---|
| Message-ID | <CAF9ehCU9Dg+LbpzekYYxtfyT4+Rm-WcCT1EEKLGvmAGc7C_YVQ@mail.gmail.com> |
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