From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25716 invoked by alias); 4 Apr 2002 20:24:47 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 25692 invoked from network); 4 Apr 2002 20:24:45 -0000 Received: from unknown (HELO dberlin.org) (64.246.6.106) by sources.redhat.com with SMTP; 4 Apr 2002 20:24:45 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by dberlin.org (8.11.6/8.11.6) with ESMTP id g34KOim18390; Thu, 4 Apr 2002 15:24:44 -0500 Date: Thu, 04 Apr 2002 12:24:00 -0000 From: Daniel Berlin To: Jim Blandy cc: gdb-patches@sources.redhat.com Subject: Re: [PATCH] Let dwarf2 CFI's execute_stack_op be used outside of CFI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-04/txt/msg00122.txt.bz2 So i'm implementing this, and want to know ... > /* Return the value N values down from the top of CONTEXT's stack. > This raises an error if there aren't at least N+1 values on the stack. */ > ADDR_TYPE dwarf_expr_fetch (struct dwarf_expr_context *context, int n); > How would you like me to raise the error? Should i add an error handling function to the dwarf_expr_context struct? Or just call "error", under the assumption that any libdwarf library we write would have error functions of it's own (all the libdwarf's do), and that it'll be the typical printf arguments error function. --Dan