This is the mail archive of the
mailing list for the binutils project.
Re: preprocessor macro to identify binutils version?
- From: Burlen Loring <bloring at lbl dot gov>
- To: Andrew Pinski <pinskia at gmail dot com>
- Cc: binutils <binutils at sourceware dot org>
- Date: Fri, 02 Aug 2013 12:42:35 -0700
- Subject: Re: preprocessor macro to identify binutils version?
- References: <51FBFF22 dot 6050107 at lbl dot gov> <CA+=Sn1=T5pOiTqwYSj1Y251b=hMCrXRojF=ONxQUgmObcG4w1g at mail dot gmail dot com>
On 08/02/2013 11:46 AM, Andrew Pinski wrote:
On Fri, Aug 2, 2013 at 11:49 AM, Burlen Loring <firstname.lastname@example.org> wrote:
This is my first binutils foray. I'm making use of libbfd to provide
detailed stack trace in an app if it crashes. In testing I've found
systems[*] with older binutils where bfd_find_nearest_line segv's. I'd like
to configure my app to disable the stack trace feature on systems with the
older binutils. Is there a preprocessor macro that can be used to idnetify
the binutils release? if not what's the best way to determine the binutils
Won't it be better to use libdwarf and not use bfd?
BFD is not designed to be used outside of binutils/gdb. Any use
outside of it I consider it a bug.
That's fairly discouraging news. I was not aware of the intention to
keep libbfd use internal to binutils/gdb. I will look into porting to
libdwarf. However, if there's a reliable way to identify binutils
versions it would be helpful. I'd like to make use of this code during