-
Type:
Improvement
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
None
-
Fully Compatible
-
TIG 2017-06-19
In this case the exception was handled appropriately and the stack trace simply adds clutter.
[2017/04/14 18:03:54.372] #10 mongo::BlockingQueue<mongo::BSONObj>::blockingPeek (maxSecondsToWait=<optimized out>, t=Traceback (most recent call last):
[2017/04/14 18:03:54.372] File "/data/mci/e6de067bfc5da5ee34edb8f24276e6de/src/buildscripts/gdb/mongo_printers.py", line 293, in __call__
[2017/04/14 18:03:54.372] return printer.printer(val)
[2017/04/14 18:03:54.373] File "/data/mci/e6de067bfc5da5ee34edb8f24276e6de/src/buildscripts/gdb/mongo_printers.py", line 106, in __init__
[2017/04/14 18:03:54.373] self.size = struct.unpack('<I', inferior.read_memory(self.ptr, 4))[0]
[2017/04/14 18:03:54.373] gdb.error: value has been optimized out
[2017/04/14 18:03:54.373] <synthetic pointer>..., this=0x6c25638) at src/mongo/util/queue.h:219
[2017/04/14 18:03:54.374] #11 mongo::repl::OplogBufferBlockingQueue::waitForData (this=0x6c25630, waitDuration=...) at src/mongo/db/repl/oplog_buffer_blocking_queue.cpp:100