From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8504 invoked by alias); 2 May 2014 16:58: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 8494 invoked by uid 89); 2 May 2014 16:58:17 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 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-ob0-f182.google.com Received: from mail-ob0-f182.google.com (HELO mail-ob0-f182.google.com) (209.85.214.182) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Fri, 02 May 2014 16:58:16 +0000 Received: by mail-ob0-f182.google.com with SMTP id wn1so692552obc.27 for ; Fri, 02 May 2014 09:58:14 -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=KzDXYvu+1WXtuJHaAE80bD7Homoa7EJY7Yt9OSqM10g=; b=UKy4OXYWMX3wU5MQxT1RHTpMQP2sByJxtKuywEZMvWY0uyU/FlUGx0gW2bAw1R6tC6 4kv958Uo9aw1YXC5UP0Dc03t/HyIpV2p0gSpwtc4E/f6xWQ9xzNhGwUJrfNdiAm4N0fJ P0scKRlW27YcT5MMugnZTD1kSX7+5ci0TfGSz60ka44ZTUQfcBmEbtLfwmTV22p27ZQH QkzImfyav8wuaIAyJY8YKI0L0bC9n5hRVHsYJXJ/NoT9KIdbHeK0X21vKByy+cAqnzpL PFealA0XwjOQH1CNQFQMX1GKHKLqiXNosr4RfhhHKzd99/uGDZNFCz04w2Wo2Cp3UK1n u2bA== X-Gm-Message-State: ALoCoQnPj8htkdjbYDVy/KYHKIQgnLiEs6bOsKoX+kC8yalTYbnt8PsTHu8CDpo9nlPpa+yzvTEk MIME-Version: 1.0 X-Received: by 10.60.52.207 with SMTP id v15mr17998429oeo.19.1399049894757; Fri, 02 May 2014 09:58:14 -0700 (PDT) Received: by 10.182.84.197 with HTTP; Fri, 2 May 2014 09:58:14 -0700 (PDT) In-Reply-To: <535FC3AC.6030200@redhat.com> References: <20131226183618.D264CA18A0@sasha2.mtv.corp.google.com> <5359101B.1080603@redhat.com> <535FC3AC.6030200@redhat.com> Date: Fri, 02 May 2014 16:58: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/msg00019.txt.bz2 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.