https://bugs.kde.org/show_bug.cgi?id=333816
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sit...@kde.org
--- Comment #4 from Harald Sitter <sit...@kde.org> ---
- walk frames
- find a QV4::ExecutionEngine frame
- get `this` argument
- run through qt_v4StackTraceForEngine (as of qt5.15+ anyway)
> p qt_v4StackTraceForEngine((void *)0x734c60)
> $1 = 0x969d40 "stack=[frame={level=\"0\",func=\"expression for
> text\",file=\"qrc:/main.qml\",fullname=\"qrc:/main.qml\",line=\"162\",language=\"js\"}]"
Alas, tricky to do cause we need gdb scripting to do it reliable and currently
we have no code for that. We instrument gdb through a static command file -
very old school.
There is also the problem that this only works for just-in-time debugging
(process tracing) as opposed to postmortem (core tracing) while moving to the
latter by default is kind of where things are headed.
--
You are receiving this mail because:
You are watching all bug changes.
