From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21964 invoked by alias); 7 May 2012 20:18:16 -0000 Received: (qmail 21955 invoked by uid 22791); 7 May 2012 20:18: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; Mon, 07 May 2012 20:18:03 +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 q47KI2hf009254 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 7 May 2012 16:18:02 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q47KI0Nw020146 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 7 May 2012 16:18:01 -0400 From: Tom Tromey To: Abhijit Halder Cc: "gdb-patches\@sourceware.org ml" Subject: Re: GDB plugin References: Date: Mon, 07 May 2012 20:18:00 -0000 In-Reply-To: (Abhijit Halder's message of "Mon, 7 May 2012 21:51:11 +0530") Message-ID: <87vck7wxs7.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.95 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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 X-SW-Source: 2012-05/txt/msg00197.txt.bz2 >>>>> "Abhijit" == Abhijit Halder writes: Abhijit> Is there any way to load a GDB plugin (shared library having extended Abhijit> functionality) in current GDB? I am planning to develop one. Need Abhijit> yours opinion on this. There is a little bit of this for the JIT functionality. Generic plugins are trouble because they tend to fix the API -- but we want to be able to change the API as needed. The JIT approach avoided this by exporting a custom, minimal API. What exactly are you planning to do? Tom