From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14987 invoked by alias); 8 Nov 2003 00:27:55 -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 14960 invoked from network); 8 Nov 2003 00:27:54 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 8 Nov 2003 00:27:54 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id D2F3D2B8F; Fri, 7 Nov 2003 19:27:54 -0500 (EST) Message-ID: <3FAC388A.10207@redhat.com> Date: Sat, 08 Nov 2003 00:27:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kevin Buettner Cc: davidm@hpl.hp.com, "J. Johnston" , gdb-patches@sources.redhat.com Subject: Re: RFA: ia64 portion of libunwind patch References: <3FA2B71A.3080905@redhat.com> <3FA2CA1B.7000502@redhat.com> <16290.59502.799536.383397@napali.hpl.hp.com> <3FAC12D3.2070207@redhat.com> <16300.8192.489647.740612@napali.hpl.hp.com> <3FAC2454.2030009@redhat.com> <16300.9949.513264.716812@napali.hpl.hp.com> <3FAC2D03.8070607@redhat.com> <16300.12503.585501.180768@napali.hpl.hp.com> <3FAC33B3.2030403@redhat.com> <1031108001337.ZM18506@localhost.localdomain> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-11/txt/msg00149.txt.bz2 > Because it may not have the elf binary (at least not locally), and it >> may not have debug info. People still expect GDB to do something >> reasonable in those cases. > > > I'm a little bit puzzled about why we wouldn't have the elf binary... > > But, assuming for the moment that we do, we'll definitely have the > unwind info since it's mandated by the ABI. "at least not locally". The unwind info can always be found in the target's memory. There are two choices here: - make the interface more remote friendly - just ignore the issue until someone complains Hmm, a good question to ask is "how cross debug friendly" is libunwind.? If its anything like libthread-db then this discussion is mute. Andrew