On Tue, May 21, 2013 at 9:52 AM, Alexander Monakov wrote:
>
> 1. The documentation does not say whether reusing "state" objects is allowed.
> For instance, I'm using backtrace_simple, and then in the callback I'm
> invoking dladdr and backtrace_pcinfo to gather file-line info if available.
> Looks
On Mon, 20 May 2013, Ian Lance Taylor wrote:
> To be clear: are you withdrawing your earlier patch?
Yes; at this point I don't think it improves anything sufficiently to spend
more time on it.
Forgive me a digression, but having now actually used libbacktrace, I have
the following questions.
1.
On Mon, May 20, 2013 at 10:07 AM, Alexander Monakov wrote:
> I now realize that a less intrusive approach is available: just provide
> replacement filenames.h, dwarf2.h in a separate directory and pick up those
> headers for a standalone build. In replacement dwarf2.h, include system
> dwarf.h, #
I now realize that a less intrusive approach is available: just provide
replacement filenames.h, dwarf2.h in a separate directory and pick up those
headers for a standalone build. In replacement dwarf2.h, include system
dwarf.h, #define potentially missing enum values and provide dummy enum tags.
> > In the case where IN_GCC is defined, where are the types
> > dwarf_attribute, dwarf_form, and dwarf_tag defined?
>
> In GCC's own dwarf2.h as enum tags; dwarf.h uses anonymous enums.
Ah, I still should have typedef'ed those types to enum tags when IN_GCC. I've
verified the following patch bo
On Tue, May 14, 2013 at 12:45 AM, Tom Tromey wrote:
>> "Alexander" == Alexander Monakov writes:
>
> Alexander> In GCC's own dwarf2.h as enum tags; dwarf.h uses anonymous enums.
>
> I'm curious to know which dwarf2.h you are testing against and/or intend
> to support. I think there is more th
> "Alexander" == Alexander Monakov writes:
Alexander> In GCC's own dwarf2.h as enum tags; dwarf.h uses anonymous enums.
I'm curious to know which dwarf2.h you are testing against and/or intend
to support. I think there is more than one.
Tom
On Wed, 8 May 2013, Ian Lance Taylor wrote:
> > +#ifdef IN_GCC
>
> Where is IN_GCC defined?
I've amended configure.ac to provide a new configuration flag
('--enable-standalone') and add -DIN_GCC to EXTRA_FLAGS unless that flag is
given. Previously I've misread grep output and thought that IN_GCC
On Wed, May 8, 2013 at 2:35 PM, Ondřej Bílka wrote:
>
> Is it possible to link staticaly without external dependencies? This
> simplifies generating backtrace when inside linker.
I'm not sure I understand the question. Is it possible to link
libbacktrace statically? Sure. That is what happens
On Wed, May 08, 2013 at 07:56:18PM +0400, Alexander Monakov wrote:
> Hello,
>
> I'd like to make libbacktrace easier to import for use in other software.
> Right now it's mostly standalone, but depends on rest of GCC in the following:
>
> 1. Build system.
> 2. Trivially depends on "filenames.h".
On Wed, May 8, 2013 at 8:56 AM, Alexander Monakov wrote:
>
> I'd like to make libbacktrace easier to import for use in other software.
> Comments?
> +#ifdef IN_GCC
Where is IN_GCC defined?
> +# Test if DWARF2 extensions enumeration values are declared
> +if test -n "${with_target_subdir}"; th
Hello,
I'd like to make libbacktrace easier to import for use in other software.
Right now it's mostly standalone, but depends on rest of GCC in the following:
1. Build system.
2. Trivially depends on "filenames.h".
3. Depends on "dwarf2.{def,h}" to obtain DW_* enumeration values.
My autotools-f
12 matches
Mail list logo
