From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19902 invoked by alias); 19 May 2014 21:30:58 -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 19888 invoked by uid 89); 19 May 2014 21:30:57 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-oa0-f53.google.com Received: from mail-oa0-f53.google.com (HELO mail-oa0-f53.google.com) (209.85.219.53) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Mon, 19 May 2014 21:30:56 +0000 Received: by mail-oa0-f53.google.com with SMTP id m1so6790684oag.26 for ; Mon, 19 May 2014 14:30:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Y4XfkVvmu7+zCwZiU8A/bkX67B3IWr1RchKtQh6hj1E=; b=N+u8nGSl2cRx1WY/86beeNH9iRUrXNs+/343la6HHKU1nt7yiFB+WZfKlj+T/+RAR4 u9ZorJ63L24+QHNo+Jcur6TagzHg6v+jhrWUcLz9tyVWPUWX+hrlugIi1GDEzPu3VsEv M6wPHjhAIwka5uWOR2DwmXDxLFg13Gn1OfrpovpAbc3Vc7gBwamLqzZ5D9k0rS/WmgzB wr4rdGXaZWr4ckm69dIeLQkmTDwO+2IViwxe2FybKuy7XP1W2gfXfQ3rDK5dId6TegbW ngs3djxR1DAZO5+/8xrGc7ko61V/NUU7KvlH9ozEvK105iiP5jBSmtrhU45F5LWna/JB NIgg== X-Gm-Message-State: ALoCoQlcAM3LFAmei6ElJ2Exk8gyGJeF9NrCBdpNhhup4K255dJ/b89diScy7/vuILZ6UsucDbmg MIME-Version: 1.0 X-Received: by 10.60.54.228 with SMTP id m4mr38701484oep.29.1400535054428; Mon, 19 May 2014 14:30:54 -0700 (PDT) Received: by 10.182.144.133 with HTTP; Mon, 19 May 2014 14:30:54 -0700 (PDT) In-Reply-To: References: <20131226183618.D264CA18A0@sasha2.mtv.corp.google.com> <5359101B.1080603@redhat.com> <535FC3AC.6030200@redhat.com> Date: Mon, 19 May 2014 21:30:00 -0000 Message-ID: Subject: Re: [RFC][PATCH] Allow JIT unwinder provide symbol information From: Alexander Smundak To: Pedro Alves Cc: gdb-patches Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2014-05/txt/msg00382.txt.bz2 Ping. On Fri, May 2, 2014 at 9:58 AM, Alexander Smundak wrote: > On Tue, Apr 29, 2014 at 8:22 AM, Pedro Alves wrote: >> But it doesn't actually provide symbol information. Not in the sense >> that it hooks with GDB's symbol lookup mechanisms. > I cannot find a better way to hook into GDB symbols lookup machinery. > It looks to me that GDB is operating on assumption that symbol information > is static (except for shared objects loading), and it not frame-specific. > The code emitted by JIT does not conform to these assumptions. > IMHO what I am proposing has the beginnings of the approach to > overcome this difficulty by allowing unwinder to have its own symbol handler. > It this approach looks reasonable, obviously more changes are needed, > but I'd like to have a confirmation that the approach is reasonable.