From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-testers-return-81378-listarch-gdb-testers=sources.redhat.com@sourceware.org>
Received: (qmail 42389 invoked by alias); 4 May 2017 08:24:55 -0000
Mailing-List: contact gdb-testers-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-testers.sourceware.org>
List-Subscribe: <mailto:gdb-testers-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-testers/>
List-Post: <mailto:gdb-testers@sourceware.org>
List-Help: <mailto:gdb-testers-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-testers-owner@sourceware.org
Received: (qmail 42142 invoked by uid 89); 4 May 2017 08:24:40 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=
X-HELO: kwanyin.sergiodj.net
Received: from kwanyin.sergiodj.net (HELO kwanyin.sergiodj.net) (158.69.185.54) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 04 May 2017 08:24:39 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [binutils-gdb/gdb-8.0-branch] Python: Use correct ptid in btrace recording
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Message-Id: <ee53a929a4c74456661f60741ec22139e06ebc70@gdb-build>
Date: Thu, 04 May 2017 08:24:00 -0000
X-SW-Source: 2017-q2/txt/msg02077.txt.bz2

*** TEST RESULTS FOR COMMIT ee53a929a4c74456661f60741ec22139e06ebc70 ***

Author: Tim Wiederhake <tim.wiederhake@intel.com>
Branch: gdb-8.0-branch
Commit: ee53a929a4c74456661f60741ec22139e06ebc70

Python: Use correct ptid in btrace recording

The user would always get the instruction_history and function_call_history
objects of the current thread, not the thread for which the gdb.Record object
was created.

The attached testcase fails without this patch and passes with the patch.