I do not know how to debug args array in a FunctionCallbackInfo with gdb

[juanarbol]

• Node.js Version: Current
• OS: Linux
• Scope (install, code, runtime, meta, other?): Debug internals
• Module (and version) (if relevant):

For some reason, gdb is grabbing the wrong object in debug

Thread 1 "node_g" hit Breakpoint 1, node::StreamBase::WriteString<(node::encoding)1> (this=0x5c9da78, args=...) at ../src/stream_base.cc:218
218       Environment* env = Environment::GetCurrent(args);
(gdb) framwe
Undefined command: "framwe".  Try "help".
(gdb) frame
#0  node::StreamBase::WriteString<(node::encoding)1> (this=0x5c9da78, args=...) at ../src/stream_base.cc:218
218       Environment* env = Environment::GetCurrent(args);
(gdb) n
219       CHECK(args[0]->IsObject());
(gdb) ptype args
type = const struct node::AssertionInfo {
    const char *file_line;
    const char *message;
    const char *function;
}
(gdb) p args->function
$14 = 0x32607c8 "int node::StreamBase::WriteString(const FunctionCallbackInfo<v8::Value> &) [enc = node::UTF8]"
(gdb) p args[0]->IsObject()
No symbol "operator[]" in current context.
(gdb) 

[juanarbol]

May refs: nodejs/node#40336

[github-actions]

It seems there has been no activity on this issue for a while, and it is being closed in 30 days. If you believe this issue should remain open, please leave a comment.
If you need further assistance or have questions, you can also search for similar issues on Stack Overflow.
Make sure to look at the README file for the most updated links.

[github-actions]

It seems there has been no activity on this issue for a while, and it is being closed. If you believe this issue should remain open, please leave a comment.
If you need further assistance or have questions, you can also search for similar issues on Stack Overflow.
Make sure to look at the README file for the most updated links.