Using debug.dump_callstack() with -d callstack causes a C error

[RpxdYTX]

Using debug.dump_callstack() with -d callstack errors with

================== C compilation error (from cc): ==============
cc:        |                                       ~~                                                                            ^~~~~~~~~
cc: /data/data/com.termux/files/usr/tmp/v_10246/hex.01JGC68SV7BHYMXC3HWJVJ2FB0.tmp.c:26377:15: error: expected expression
cc:  26377 |         bool ret = f(, );
cc:        |                      ^
cc: /data/data/com.termux/files/usr/tmp/v_10246/hex.01JGC68SV7BHYMXC3HWJVJ2FB0.tmp.c:26377:17: error: expected expression
cc:  26377 |         bool ret = f(, );
cc:        |                        ^
cc: /data/data/com.termux/files/usr/tmp/v_10246/hex.01JGC68SV7BHYMXC3HWJVJ2FB0.tmp.c:26408:15: error: expected expression
cc:  26408 |         bool ret = f(, );
cc:        |                      ^
cc: /data/data/com.termux/files/usr/tmp/v_10246/hex.01JGC68SV7BHYMXC3HWJVJ2FB0.tmp.c:26408:17: error: expected expression
cc:  26408 |         bool ret = f(, );
... (the original output was 26 lines long, and was truncated to 12 lines)
================================================================
(You can pass `-cg`, or `-show-c-output` as well, to print all the C error messages).

On function

import v.debug

@[noreturn]
pub fn todo() {
    debug.dump_callstack()
    panic("TODO")
}

Runinng without -d callstack makes the code run, but then todo is useless

Originally posted by @RpxdYTX in #23312 (comment)

Note

You can use the 👍 reaction to increase the issue's priority for developers.

Please note that only the 👍 reaction to the issue itself counts as a vote.
Other reactions and those to comments will not be taken into account.

[felipensp]

This is because the func call is related to a callback with parameters. The trace generated fns must receive the parameters to be passed to the callback one.