-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Fully Compatible
-
v4.2
-
STM 2019-07-29
-
1
[2019/06/05 03:28:31.295] Running Print JavaScript Stack Supplement [2019/06/05 03:28:31.295] Ignoring GDB error 'No type "mozjs" within class or namespace "mongo".' in javascript_stack [2019/06/05 03:28:31.295] Ignoring GDB error 'No type "mozjs" within class or namespace "mongo".' in javascript_stack [2019/06/05 03:28:31.295] Ignoring GDB error 'No type "mozjs" within class or namespace "mongo".' in javascript_stack [2019/06/05 03:28:31.295] Ignoring GDB error 'No type "mozjs" within class or namespace "mongo".' in javascript_stack [2019/06/05 03:28:31.295] Ignoring GDB error 'No type "mozjs" within class or namespace "mongo".' in javascript_stack [2019/06/05 03:28:31.295] Ignoring GDB error 'No type "mozjs" within class or namespace "mongo".' in javascript_stack
Original description
In gdb, if we're in a frame that does not know about mongo::mozjs:kCurrentScope, then we will not print a javascript stack trace.
This can be especially useful when debugging our integration tests and gdb optimizes variables out of the core dump.
max.hirschhorn figured out that switching the frame in gdb (frame 1) and then running mongodb-javascript-stack will work fine.
Perhaps we can arbitrarily switch frames here before trying to print the stack trace.