This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: stabs vs. dwarf-2 clarification

From: Nick Clifton <nickc at redhat dot com>
To: Jeff Baker <jbaker at qnx dot com>
Cc: "'binutils at sourceware dot org'" <binutils at sourceware dot org>
Date: Mon, 04 Apr 2005 18:44:21 +0100
Subject: Re: stabs vs. dwarf-2 clarification
References: <1578FF984ABAD411AFA5000102C4BB5B04E41602@nimbus>

Hi Jeff,

I have a (hopefully) quick question about the behaviour of stabs as compared
to dwarf-2.  I have a small sample app that I build with stabs debugging and
link against a static lib that was built with no debugging.  If I use
addr2line to get the line number for anything from inside the static lib
with stabs debugging I will get the line number of whatever the previous
stabs entry is, no matter how far back it has to go.  With dwarf-2 I get
"??:0".  Is this the way stabs is expected to work?

I've attached a testcase that shows what I'm talking about.  Modify the
Makefile to fit your host system, make it and then ask for a line number
from inside func1.  You should get appprofiler_looper.c:126.

I tried to reproduce this but failed(*). I was however using the latest binutils sources from the CVS repository and I know that Fred Fish has been checking patches to fix things in this area, so perhaps that is why.

Cheers
  Nick

(*) failed as in when I was compiling with "-gstabs" I still got "??:0" as the lien associated with the address-known-to-be-inside-func1.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]