lupyuen / remote-bl602 Goto Github PK

I'm being lazy and not testing this code, but by inspection, I'm not sure it does the right thing with demangling C++ symbols in the stack trace. Just running the collection of test.log through riscv64...-c++-filt (or doing it in a later pass over the file) should get you constructor and destructor call as well as operator overloads.

It's a matter of taste where to insert that filter. Doing it here means the output you see on the terminal will be unpleasant. It may be easier to insert it at the uses down around L131 or 140.

If this script needs to be faster, you can probably harvest the symbol table from riscv64...objdump -t (print symbols) or the more common riscv64...nm - that has a zillion options of its own. That should be less expensive than passing over a full disassembly. It may not be an issue if you're running this on a "big" computer and not the BL602 itself.

script may be easier to wrangle than cat on a serial port. There tends to be fewer flushing issues as cat normally buffers data on write in large (page or so) chunks. script has special flags for writing to pipes.

Yay for tackling an underserved problem in that project. The top-of-tree was frequently broken when I tried to be involved.