Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH] btrace: avoid tp != NULL assertion
Date: Tue, 03 Mar 2015 13:55:00 -0000	[thread overview]
Message-ID: <A78C989F6D9628469189715575E55B231E6EF452@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <54F5BA0B.2000106@redhat.com>

> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] On Behalf Of Pedro Alves
> Sent: Tuesday, March 3, 2015 2:42 PM
> To: Metzger, Markus T
> Cc: gdb-patches@sourceware.org
> Subject: Re: [PATCH] btrace: avoid tp != NULL assertion


> > No, that wasn't the reason for replacing the assert.  There are no such
> > errors in the gdb.btrace suite (which is mostly single-threaded) with my
> > patch and I have not seen any such errors otherwise, either.
> 
> Then it sounds like we're either lacking basic tests, or the threaded tests
> are somehow not running correctly when gdb is a 32-bit program.  I think
> that if you step any non-leader thread, you should see it happen.
> Grepping the tests, I think gdb.btrace/multi-thread-step.exp should have
> caught it.  My machine doesn't do btrace, so I can't try it myself...
> 
> BTW, did any existing test in the testsuite catch the assertion we're
> fixing?

Almost all of them when run on 32-bit systems; -m32 on 64-bit systems does
not catch this.

Regards,
Markus.
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052


  reply	other threads:[~2015-03-03 13:55 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 [this message]
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

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=A78C989F6D9628469189715575E55B231E6EF452@IRSMSX104.ger.corp.intel.com \
    --to=markus.t.metzger@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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