From: Yao Qi <qiyaoltc@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: one week to go until GDB 7.11 branch creation...
Date: Wed, 20 Jan 2016 16:32:00 -0000 [thread overview]
Message-ID: <86fuxsrz38.fsf@gmail.com> (raw)
In-Reply-To: <20160118034414.GG4059@adacore.com> (Joel Brobecker's message of "Mon, 18 Jan 2016 07:44:14 +0400")
Joel Brobecker <brobecker@adacore.com> writes:
Hi Joel,
> If there are other issues we are not aware of, please let us know!
Here are some issues,
- some fails in test cases added by fort_dyn_array patch on some OS and
targets. I reported them here
https://sourceware.org/ml/gdb-patches/2016-01/msg00467.html
and the original patch is
https://sourceware.org/ml/gdb-patches/2015-10/msg00085.html
- PR 19491, fail in gdb.base/multi-forks.exp
- GDB sets breakpoint on the wrong place, if the file basename is
identical to the current file basename. PR 19474.
I posted a patch
https://www.sourceware.org/ml/gdb-patches/2015-12/msg00321.html
but it causes a regression.
- As a result of the previous bug, GDB crashes in gdb.base/dprintf.exp.
I posted a patch
https://sourceware.org/ml/gdb-patches/2016-01/msg00323.html
to avoid GDB crash.
- A regression in trunk about arm stepping out of signal handler, patch
is posted https://sourceware.org/ml/gdb-patches/2016-01/msg00377.html
and I'll push it in after the regression testing.
- A fail in gdb.threads/interrupted-hand-call.exp
$ make check RUNTESTFLAGS='--target_board=remote-gdbserver-on-localhost interrupted-hand-call.exp'
(gdb) PASS: gdb.threads/interrupted-hand-call.exp: dummy frame popped
continue^M
Continuing.^M
FAIL: gdb.threads/interrupted-hand-call.exp: continue until exit (timeout)
Remote debugging from host 127.0.0.1^M
ptrace(regsets_fetch_inferior_registers) PID=9710: No such process^M
ptrace(regsets_fetch_inferior_registers) PID=9710: No such process^
I suspect it is about a GDB PR about disappeared inferior, but I can't
find the PR in bugzilla. I'll look into it.
I'll update https://www.sourceware.org/gdb/wiki/GDB_7.11_Release later.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-01-20 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 3:44 Joel Brobecker
2016-01-20 16:32 ` Yao Qi [this message]
2016-01-21 10:05 ` Joel Brobecker
2016-01-21 15:10 ` Yao Qi
2016-01-21 15:22 ` Pedro Alves
2016-01-21 15:24 ` Pedro Alves
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=86fuxsrz38.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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).