From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18339 invoked by alias); 29 Mar 2017 14:50:49 -0000 Mailing-List: contact elfutils-devel-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Post: List-Help: List-Subscribe: Sender: elfutils-devel-owner@sourceware.org Received: (qmail 18236 invoked by uid 89); 29 Mar 2017 14:50:49 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.99.2 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=H*F:U*mail X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on sourceware.org X-Spam-Level: X-HELO: dd17628.kasserver.com From: Milian Wolff To: elfutils-devel@sourceware.org Subject: dwfl_attach_state alternative taking Ebl? Date: Wed, 29 Mar 2017 14:50:00 -0000 Message-ID: <2572422.AxEj1gHkJW@milian-kdab2> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-SW-Source: 2017-q1/txt/msg00142.txt.bz2 Hey all, would you be willing to accept a patch that adds an alternative to dwfl_attach_state taking an Ebl pointer instead of the Elf* to guess the architecture from? This would simplify the code for cases where we know the architecture, but don't necessarily have a corresponding Elf* at hand (yet). If there'd be a version that takes the Ebl pointer directly, one could use e.g. ebl_openbackend_emulation or _machine to find the backend handle for the known target architecture directly. If this would be acceptable, I will write a patch up for this. I would need suggestions for a fitting name though, in C++ I'd simply use an overload but here with plain C... ;-) Thanks -- Milian Wolff mail@milianw.de http://milianw.de