From: Keith Seitz <keiths@redhat.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Phil Muldoon <pmuldoon@redhat.com>, John Baldwin <jhb@freebsd.org>
Subject: Re: [PATCH 1/2] Include the fs_base and gs_base registers in amd64 target descriptions.
Date: Wed, 12 Jul 2017 16:23:00 -0000 [thread overview]
Message-ID: <59664D04.7030606@redhat.com> (raw)
In-Reply-To: <CAH=s-PPM7u=f=_4k+=wLvv4z822VJRqbkxrsSv9C0eKqX-tMCA@mail.gmail.com>
On 07/12/2017 06:02 AM, Yao Qi wrote:
> On Wed, Jul 12, 2017 at 1:16 PM, Phil Muldoon <pmuldoon@redhat.com> wrote:
>>
>> Does anyone else see this?
>>
Yes, I do, too -- I ran into it yesterday while rebasing patches for posting. FWIW, buildbot sees it, too (snippet from x86_64/-m32 linux):
set architecture i386:x64-32
ERROR: Process no longer exists
UNRESOLVED: gdb.base/all-architectures-2.exp: tests: osabi=GNU/Linux: arch=i386:x64-32: endian=auto: set architecture i386:x64-32
ERROR: Couldn't send set endian auto to GDB.
UNRESOLVED: gdb.base/all-architectures-2.exp: tests: osabi=GNU/Linux: arch=i386:x64-32:intel: endian=auto: set endian
ERROR: Couldn't send set architecture i386:x64-32:intel to GDB.
UNRESOLVED: gdb.base/all-architectures-2.exp: tests: osabi=GNU/Linux: arch=i386:x64-32:intel: endian=auto: set architecture i386:x64-32:intel
ERROR: Couldn't send show endian to GDB.
UNRESOLVED: gdb.base/all-architectures-2.exp: tests: osabi=GNU/Linux: arch=i386:x64-32:intel: endian=auto: show endian
ERROR: Couldn't send ptype 1.0L to GDB.
...
In fact right now, HEAD is unusable:
$ ./gdb gdb
Segmentation fault
$ ./gdb --version | head -1
GNU gdb (GDB) 8.0.50.20170711-git
> I don't see the issue you posted here, but there are
> some regressions shown in buildbot.
> https://sourceware.org/ml/gdb-testers/2017-q3/msg00370.html
>
> John, could you take a look?
I'm not normally one to suggest this, but I think this is an exceptional case. Please consider reverting this patch until this issue is resolved.
Keith
next prev parent reply other threads:[~2017-07-12 16:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 22:50 [PATCH 0/2] Support fs_base and gs_base for native FreeBSD/amd64 John Baldwin
2017-06-27 22:51 ` [PATCH 2/2] Support the fs_base and gs_base registers on FreeBSD/amd64 native processes John Baldwin
2017-07-11 8:09 ` Yao Qi
2017-06-27 22:51 ` [PATCH 1/2] Include the fs_base and gs_base registers in amd64 target descriptions John Baldwin
2017-07-11 8:03 ` Yao Qi
2017-07-11 16:26 ` John Baldwin
2017-07-12 12:16 ` Phil Muldoon
2017-07-12 13:02 ` Yao Qi
2017-07-12 13:51 ` Simon Marchi
2017-07-12 20:03 ` John Baldwin
2017-07-13 16:55 ` Yao Qi
2017-07-13 17:04 ` John Baldwin
2017-07-13 18:40 ` Pedro Alves
2017-07-13 19:59 ` Pedro Alves
2017-07-12 16:23 ` Keith Seitz [this message]
2017-07-11 7:49 ` [PATCH 0/2] Support fs_base and gs_base for native FreeBSD/amd64 Yao Qi
2017-07-11 16:26 ` John Baldwin
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=59664D04.7030606@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.org \
--cc=pmuldoon@redhat.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).