From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26426 invoked by alias); 9 Jun 2017 09:40:18 -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 26385 invoked by uid 89); 9 Jun 2017 09:40:15 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.1 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=Hx-languages-length:739, our X-HELO: mail.rt-rk.com Received: from mx2.rt-rk.com (HELO mail.rt-rk.com) (89.216.37.149) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 09 Jun 2017 09:40:13 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.rt-rk.com (Postfix) with ESMTP id 037A01A4B23; Fri, 9 Jun 2017 11:40:15 +0200 (CEST) Received: from [10.10.13.44] (rtrkw616-lin.domain.local [10.10.13.44]) by mail.rt-rk.com (Postfix) with ESMTPSA id DD9161A4B1C; Fri, 9 Jun 2017 11:40:14 +0200 (CEST) Subject: Re: [PATCH] TLS access support in cross- Linux GDB To: Pedro Alves , Gary Benson References: <593529D1.7040206@rt-rk.com> <20170608102003.GA24047@blade.nx> <86cbd96e-d8c8-57f5-5951-2b19592425cd@redhat.com> Cc: gdb-patches@sourceware.org, nemanja.popov@rt-rk.com, nikola.prica@rt-rk.com, petar.jovanovic@rt-rk.com, asowda@cisco.com, ibaev@cisco.com From: Djordje Todorovic Message-ID: <593A6D02.4050209@rt-rk.com> Date: Fri, 09 Jun 2017 09:40:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: <86cbd96e-d8c8-57f5-5951-2b19592425cd@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-SW-Source: 2017-06/txt/msg00225.txt.bz2 Thank you for your comments! We are aware of dependency and maintenance problems that this patch causes. The reason we took this approach is problem with debugging programs with di= fferent glibc versions.=20 We thought that handling this issue with different versions of glibc was mo= re appropriate to do in=20 gdb, since gdb should handle programs with different versions of glibc and = libthread_db has been=20 designed to work with the one version. Implementing this support as new cross-functionality in glibc/libthread_db = was our plan B and we=20 will implement this approach also. We just wanted to start discussion about= this with community and=20 get some feedback. Thanks, Djordje Todorovi=C4=87