bugmake - Bugs: bug #55316, Stack (or rather...


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

Submitted by:  Michael Livshin <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
Component Version:  4.3 Operating System:  Any
Fixed Release:  None Triage Status:  None

Add a New Comment (Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


Fri 28 Dec 2018 08:25:05 PM UTC, original submission:  

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.

Michael Livshin <cmm2>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

Attached Files


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by cmm2 (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.




    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-12-30 cmm2 Attached File- => Added 0001-Print-backtrace-on-fatal-error.patch, #45798
    2018-12-28 cmm2 Attached File- => Added 0001-Print-backtrace-on-fatal-error.patch, #45761

    Back to the top

    Powered by Savane 3.5