[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #55316] Stack (or rather "scope"?) backtracing facility

From: Michael Livshin
Subject: [bug #55316] Stack (or rather "scope"?) backtracing facility
Date: Fri, 28 Dec 2018 15:25:07 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0


                 Summary: Stack (or rather "scope"?) backtracing facility
                 Project: make
            Submitted by: cmm2
            Submitted on: Fri 28 Dec 2018 08:25:05 PM UTC
                Severity: 3 - Normal
              Item Group: Enhancement
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
       Component Version: SCM
        Operating System: Any
           Fixed Release: None
           Triage Status: None



It's a decade since GNU Make grew a capable (if a tad... minimal) macro
language, and people out there are actually using it (ever seen the Android
build system, for instance?  That thing is insane.  More examples exist, just
not publicly).

One thing I've dearly wished for, many times, is getting a proper stack
(however you'd define that) trace upon a fatal error.  Turns out it's not
exactly hard to implement, so here goes.

The attached implementation knows about target, function & "foreach" scopes,
and tries to format them intelligently.  It does not check for "private" or
"special" variables; I don't know if that's a problem.


File Attachments:

Date: Fri 28 Dec 2018 08:25:05 PM UTC  Name:
0001-Print-backtrace-on-fatal-error.patch  Size: 12KiB   By: cmm2



Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]