Introduce a new 'colored' Backtrace format #64
Conversation
|
Can one of the admins verify this patch? |
9 similar comments
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Hi there, So I don't think we necessarily want to be adding much more functionality in this project, rather, we're slowly sunsetting it. Perhaps such format improvements are something that can be brought up in the thread I linked, to make sure the format of the official output is as nice as you'd hope it to be? |
This allows customizing the printed backtrace format, and separates backtrace formatting (platform agnostic) and printing (platform specific).
The current format is now called
fulland I made a new one calledcolored(I'm not quite happy with the name, I'm open to suggestions) with colors and a newline between the function name and file. It's easier on the eyes when reading on a small integrated terminal. It also removes the top 4 stack entries that are mostly irrelevant (since they belong to either Backtrace or libc / Windows CRT).This has been tested and works fine on both Linux and Windows.