From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 108335 invoked by alias); 5 Jul 2019 16:46:05 -0000 Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org Received: (qmail 108314 invoked by uid 89); 5 Jul 2019 16:46:05 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-9.1 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_1,KAM_SHORT,SPF_PASS autolearn=ham version=3.3.1 spammy=begins, H*Ad:U*systemtap, offers, appreciated! X-HELO: gnu.wildebeest.org Received: from wildebeest.demon.nl (HELO gnu.wildebeest.org) (212.238.236.112) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 05 Jul 2019 16:46:02 +0000 Received: from librem.wildebeest.org (deer0x15.wildebeest.org [172.31.17.151]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 5A27C302774F; Fri, 5 Jul 2019 18:46:00 +0200 (CEST) Received: by librem.wildebeest.org (Postfix, from userid 1000) id 689FAC3B16; Fri, 5 Jul 2019 18:04:55 +0200 (CEST) Date: Fri, 05 Jul 2019 16:46:00 -0000 From: Mark Wielaard To: Aaron Merey Cc: elfutils-devel@sourceware.org, systemtap@sourceware.org Subject: Re: debuginfo server progress update Message-ID: <20190705160455.GH4777@wildebeest.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-IsSubscribed: yes X-SW-Source: 2019-q3/txt/msg00006.txt.bz2 Hi Aaron, On Wed, Jul 03, 2019 at 03:59:46PM -0400, Aaron Merey wrote: > The debuginfo server, a web service that offers lightweight on-demand lookups > of debuginfo-related data, along with its elfutils client have begun to take > shape so I want to provide an update on where we currently are in its > development and how to use it. > > We plan on shipping debuginfo server with elfutils and it is currently > available on the branch 'fche/dbgserver' of the elfutils git repo. And now also simply on 'dbgserver'. https://sourceware.org/git/?p=elfutils.git;a=shortlog;h=refs/heads/dbgserver > The > http web server itself is able to scan a directory tree for any debuginfo, > executable and source files and index them by build-id. The elfutils client > hooks into libdwfl and provides a fallback so that if the library is not able > to locate a debuginfo file, the client, if enabled, will attempt to query > debuginfo servers for debuginfo containing a particular build-id. > [...] > This time systemtap successfully acquires the debuginfo and begins running > the probe. Although in this example everything is running locally, the server > and the debuginfo could just as well be on a remote host. > > Debuginfo server development is ongoing. Some of the features we have planned > include a gdb client that could query debuginfo servers for debuginfo or source > code and the ability for the server to automatically search rpms for any of the > files requested by a client. We also are planning a talk/demo at GNU Cauldron > this September in Montréal, Canada (https://gcc.gnu.org/wiki/cauldron2019). > > Hopefully this helped give you a sense of how to use debuginfo server, where it > is in its development, and what is to come. Feedback is always appreciated! I think it would be nice if there was a dbgclient binary that could be reused by multiple clients. It could do most of what you currently do in libdwfl/dbgserver-client.c. It would simply take a buildid and type (exec, dbg, src) and return a file path to the resulting file when found (or a well defined error number when not found). Such a dbgclient executable would make writing other clients easier. For example dbgserver_build_id_find would simply reduce to spawning dbgclient with the right arguments and opening the resulting file path. Other clients, like gdb, then also don't need to implement the caching and quering, but can also simply call dbgclient and just open the resulting file. Cheers, Mark