From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16585 invoked by alias); 25 May 2012 14:37:16 -0000 Received: (qmail 16555 invoked by uid 22791); 25 May 2012 14:37:15 -0000 X-SWARE-Spam-Status: No, hits=-6.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 25 May 2012 14:36:50 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q4PEaoVk007483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 25 May 2012 10:36:50 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q4PEamch004841 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 25 May 2012 10:36:49 -0400 From: Tom Tromey To: Kaushik Srenevasan Cc: gdb@sourceware.org Subject: Re: Hotspot JVM GDBJIT plugin References: Date: Fri, 25 May 2012 14:37:00 -0000 In-Reply-To: (Kaushik Srenevasan's message of "Thu, 24 May 2012 04:03:58 -0700") Message-ID: <87396o72f3.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.97 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-05/txt/msg00126.txt.bz2 >>>>> "Kaushik" == Kaushik Srenevasan writes: Kaushik> I've been working on a Hotspot JVM JIT plugin for GDB Very cool. Kaushik> I'm writing to see if there is any interest in pulling the Kaushik> changes [3] I've had to make to GDB, to get this to work. Sure. Just send individual patches following the contribution instructions... Kaushik> The first of these changes [3] is a simple fix to a crash while Kaushik> trying to display the return type of a JIT frame (say on Kaushik> 'finish'.) Sounds good. Kaushik> The second (frame based symbol handler) is a feature added to Kaushik> help GDB understand frames created by Hotspot's "template" Kaushik> interpreter. Kaushik> This adds an additional callback that the reader may choose to Kaushik> implement to return the name (file path or line number) of the Kaushik> function executing in the frame in question. Phil has been working on a related feature in gdb, called "frame filters". Frame filters let you write Python code to modify frames as they are being displayed; you can change nearly any aspect of a frame, and even insert and delete frames. The primary use case for this feature is displaying better stack traces in interpreters. So, you might consider just waiting for this and writing your frame logic in Python. If you'd rather press on, that is fine too. Tom