You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When testing with non trivial source code the output of trace -tr can be long and sometimes we are only interested in a range of lines, would be nice to have a way to specify it, maybe something like:
ccparse -tr printAST,35119-35127 sqlite3.pp2.c
The text was updated successfully, but these errors were encountered:
Seems like a reasonable idea and not too hard to implement. The interface should probably not use -tr, which is a general-purpose tracing facility that doesn't know about line numbers, etc. Instead, I think I'd do something like:
ccparse --range-trace printAST,35119-35127
However, when I have a need along these lines, what I typically do is first try to obtain an input file that is as small as possible while still demonstrating some behavior of interest. The "delta" tool at https://github.com/dsw/delta can do this automatically in many cases. Consequently, I'm normally working with input files that are small enough that further restriction based on line number is unnecessary.
Just to set expectations, I probably won't work on this, but you (or anyone else) are welcome to submit a pull request.
When testing with non trivial source code the output of trace
-tr
can be long and sometimes we are only interested in a range of lines, would be nice to have a way to specify it, maybe something like:The text was updated successfully, but these errors were encountered: