From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14980 invoked by alias); 15 Dec 2001 20:56:36 -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 14959 invoked from network); 15 Dec 2001 20:56:35 -0000 Received: from unknown (HELO www.cgsoftware.com) (208.155.65.221) by sources.redhat.com with SMTP; 15 Dec 2001 20:56:35 -0000 Received: from localhost (localhost [127.0.0.1]) by www.cgsoftware.com (8.9.3/8.9.3) with ESMTP id PAA03542; Sat, 15 Dec 2001 15:56:26 -0500 Date: Sat, 15 Dec 2001 12:56:00 -0000 From: Daniel Berlin To: Andrew Cagney cc: Paolo Molaro , Subject: Re: large line number debugging support In-Reply-To: <3C1BA64C.1060104@cygnus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2001-12/txt/msg00145.txt.bz2 On Sat, 15 Dec 2001, Andrew Cagney wrote: > > Hi. > > I just added support to output stab information in the mono JIT > > compiler: this debugging info is used to debug code generation problems > > and as such the lines in the source code it references are from an > > assembly dump of the CLR programs. For large libraries the assembly > > files can be longer than 2^16 lines and the binary stabs format seems to use > > 16 bits unsigned integers to store line info. > > Is there some kind of know workaround for this problem? > > Splitting the assembly dump would be extremely ugly. > > > How does dwarf2 go with this? ``gas -gdwarf2'' will select dwarf2 > assembler debug info. DWARF2 can do line numbers as large as you like, the opcodes take leb128 or sleb128, as opposed to some fixed size encoding. > > Andrew > > >