> Patch tested and committed with this ChangeLog entry.
>
> 2015-08-13 Ian Lance Taylor
>
> * dwarf.c (read_function_entry): Add vec_inlined parameter.
> Change all callers.
Thanks, this is great! I am going to submit the libgfortran patch to use
libbacktrace today.
Cheers,
FX
On Thu, Aug 13, 2015 at 8:50 AM, FX wrote:
>> And yet, that patch has absolutely nothing to do with libbacktrace.
>> Hmmm. Let's try this one.
>
> Works perfectly with the patch:
Patch tested and committed with this ChangeLog entry.
2015-08-13 Ian Lance Taylor
* dwarf.c (read_function_entry
> And yet, that patch has absolutely nothing to do with libbacktrace.
> Hmmm. Let's try this one.
Works perfectly with the patch:
Program aborted. Backtrace:
#0 0xf75e5b9b _gfortrani_show_backtrace
../../../../trunk/libgfortran/runtime/backtrace.c:113
#1 0xf75e6aa7 _gfortrani_sys_abort
On Thu, Aug 13, 2015 at 8:25 AM, Ian Lance Taylor wrote:
> On Thu, Aug 13, 2015 at 7:11 AM, FX wrote:
>>
>>> I don't know why this is not working. Everything looks fine in the
>>> a.out that you sent. Unfortunately, I think you sent the one built
>>> without libbacktrace. Can you send me the o
On Thu, Aug 13, 2015 at 7:11 AM, FX wrote:
>
>> I don't know why this is not working. Everything looks fine in the
>> a.out that you sent. Unfortunately, I think you sent the one built
>> without libbacktrace. Can you send me the one built with libbacktrace?
>
> Attached is the a.out with libgf
> You might also take a look at the patch posted to PR 54572 which was my
> attempt to use libbacktrace a few years ago. While I got symbolic backtraces
> working somewhat, unfortunately I never got it to work completely since it
> crashed somewhere in libbacktrace in some cases, but maybe whate
> You should always get accurate PC values even
> on systems where libbacktrace does not yet generate file/line
> information.
Cool! We’ll be able to use it unconditionaly with all targets, which is very
nice.
> I don't know why this is not working. Everything looks fine in the
> a.out that yo
Resending in text/plain, sorry for any extra spam...
On Thu, Aug 13, 2015 at 4:44 PM, Ian Lance Taylor wrote:
>
> FX writes:
>
> > 1. It appears that even on platforms with BACKTRACE_SUPPORTED == 0
> > (such as x86_64-apple-darwin), libbacktrace is built and able to
> > perform a nonsymbolic bac
FX writes:
> 1. It appears that even on platforms with BACKTRACE_SUPPORTED == 0
> (such as x86_64-apple-darwin), libbacktrace is built and able to
> perform a nonsymbolic backtrace (which appears accurate). Is that a
> feature? Can I rely on it?
Yes, that is a feature. You should always get acc
