]> sourceware.org Git - systemtap.git/commit
@var() diagnostics: generate more dwarf detail & context
authorFrank Ch. Eigler <fche@redhat.com>
Fri, 14 Feb 2020 21:10:22 +0000 (16:10 -0500)
committerFrank Ch. Eigler <fche@redhat.com>
Fri, 14 Feb 2020 23:35:06 +0000 (18:35 -0500)
commit0e1d5b7eb39785cbafe0c0fb1c4e5e3d21576aab
treebf6e745c970ae82f4099d5f2a56fe9a36ab1eec2
parent91ffb97ad33591595d5c68c0ed3c0ffe5305cd20
@var() diagnostics: generate more dwarf detail & context

For TLS-related variables like @var("errno") in glibc, some
useful diagnostic details were just dropped on the floor as
semantic_error objects were caught but not printed.  New code
tries to arrange for these to be chained instead of lost.  In
exchange, more errors would propagate to session.print_error
as chained to the target_symbol, so now the code also has to
duplicate-eliminate the chained errors.

The net result is that at verbosity 0 or 1, we appear to get only a
few specific and valuable incremental messages, which point to the
problematic dwarf.  It would be nice to simplify this stuff, perhaps
by storing context (script-source level data, dwarf pointers, dwarf
contents, etc.) as RAII style global stack of "current details".
NEWS
dwflpp.cxx
session.cxx
tapsets.cxx
This page took 0.027052 seconds and 5 git commands to generate.