From: Pedro Alves <palves@redhat.com>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] btrace: avoid tp != NULL assertion
Date: Tue, 03 Mar 2015 15:49:00 -0000 [thread overview]
Message-ID: <54F5D7E8.4080000@redhat.com> (raw)
In-Reply-To: <A78C989F6D9628469189715575E55B231E6EF576@IRSMSX104.ger.corp.intel.com>
On 03/03/2015 03:37 PM, Metzger, Markus T wrote:
> I think that was a misunderstanding. The assertion is caught by several
> gdb.btrace tests when run with 32-bit GDB.
>
> I thought you were referring to the badness in my patch that would
> result in GDB asking for registers in a wrong process.
Ah. Alright, glad we're sorted. :-)
Thanks,
Pedro Alves
prev parent reply other threads:[~2015-03-03 15:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 9:25 Markus Metzger
2015-03-02 22:09 ` Pedro Alves
2015-03-03 10:49 ` Metzger, Markus T
2015-03-03 11:55 ` Pedro Alves
2015-03-03 12:25 ` Metzger, Markus T
2015-03-03 13:41 ` Pedro Alves
2015-03-03 13:55 ` Metzger, Markus T
2015-03-03 14:03 ` Pedro Alves
2015-03-03 14:45 ` Metzger, Markus T
2015-03-03 15:25 ` Pedro Alves
2015-03-03 15:37 ` Metzger, Markus T
2015-03-03 15:49 ` Pedro Alves [this message]
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=54F5D7E8.4080000@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.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