From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15538 invoked by alias); 4 May 2003 15:46:58 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 15531 invoked from network); 4 May 2003 15:46:58 -0000 Received: from unknown (HELO crack.them.org) (146.82.138.56) by sources.redhat.com with SMTP; 4 May 2003 15:46:58 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 19CLht-0001v3-00; Sun, 04 May 2003 10:47:18 -0500 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 19CLhW-0003CG-00; Sun, 04 May 2003 11:46:54 -0400 Date: Sun, 04 May 2003 15:46:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: Doug Evans , gdb@sources.redhat.com Subject: Re: -frame.c, frame/.c, config//frame.c, ... Message-ID: <20030504154654.GC12099@nevyn.them.org> Mail-Followup-To: Andrew Cagney , Doug Evans , gdb@sources.redhat.com References: <3EB48526.9060104@redhat.com> <16052.35297.269737.92814@casey.transmeta.com> <3EB492BC.3080502@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EB492BC.3080502@redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-05/txt/msg00039.txt.bz2 On Sun, May 04, 2003 at 12:10:36AM -0400, Andrew Cagney wrote: > >Andrew Cagney writes: > > > config//frame.[hc]: > > > Keeps the cpu stuff in a single directory. > > Some things I forgot to note: > > This is actually the one I like least. config//*.{mt,mh,h} are all > being deleted, so adding files to that directory would make for > confusion. Unlike {unwind,frame}/, it isn't clear what the exact > interface that the file should be exporting was. On the other hand, it > keeps files together. > > There is the question of where to put more generic unwinders (dwarf2cfi, > libunwind, ...) Hmm. For non-cpu-specific files, we have two choices that I can think of off the top of my head: - Toplevel directory - Functional subdirectory, i.e. unwind/ or frame/. I rather like that idea... > >Seems like this is a winner though you'd still want to call it > >-frame.c to avoid collisions in multi-arch targeted gdb's. > > ? For instance, gcc -c normally drops object files in the current directory. Makes debugging simpler too. Having multiple files named frame.c in your debug info is a little confusing. Again, something GDB could handle better, if we could figure out the interface... -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer