-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
None
-
Fully Compatible
-
ALL
-
STM 2020-07-27
-
2
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The BSON Python package can throw exceptions; the GDB pretty printer allows these exceptions to escape up into gdb/lldb, which can cause them to crash (I'm not sure why).
Here is an example where I managed to get gdb to print a python stack trace and not crash (this is difficult to achieve):
(gdb) p oplogBSON
$13 = owned BSONObj 340 bytes @ 0x555556a614a8Traceback (most recent call last):
File "buildscripts/gdb/mongo_printers.py", line 130, in children
bsondoc = buf.decode(codec_options=options)
File "/opt/mongodbtoolchain/revisions/e84eb3fd219668197589e62dba14b9914712642d/stow/python3-v3.FFC/lib/python3.7/site-packages/bson/__init__.py", line 1164, in decode
return _bson_to_dict(self, codec_options)
bson.errors.InvalidBSON: year 292278994 is out of range
- is caused by
-
PYTHON-1824 Add ability to workaround Python's datetime range limitations
-
- Released
-