From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25875 invoked by alias); 29 Apr 2014 17:05:37 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 25865 invoked by uid 89); 29 Apr 2014 17:05:37 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 29 Apr 2014 17:05:36 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s3TH5WKH012749 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 29 Apr 2014 13:05:32 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s3TH5Ubr026603; Tue, 29 Apr 2014 13:05:30 -0400 Message-ID: <535FDBD9.9040803@redhat.com> Date: Tue, 29 Apr 2014 17:05:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Hui Zhu CC: Mark Kettenis , Hui Zhu , gdb-patches ml Subject: Re: [PATCH] Fix interrupt.exp fails with m32 in x86_64 References: <53554475.3010201@mentor.com> <201404211827.s3LIRL6a007871@glazunov.sibelius.xs4all.nl> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2014-04/txt/msg00622.txt.bz2 On 04/29/2014 04:56 PM, Hui Zhu wrote: > I am sorry that the root cause of issue has something wrong. > The right root cause is: > When inferior call 32 bits syscall "read", Linux kernel function > "ia32_cstar_target" will set TS_COMPAT to current_thread_info->status. Thanks a lot of tracking this stuff down. I appreciate the effort. It'd be great if we got an ack on the kernel side on what's going on before we considered working around it in GDB. Thanks, -- Pedro Alves