get_cls_info get_obj_info
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Storm |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I have this strange stacktrace when im calling store.add(object):
Traceback (most recent call last):
File "/opt/voip/
UserLogic(
File "/opt/voip/
StoreManage
File "/opt/voip/
self.
File "/usr/lib/
obj_info = get_obj_info(obj)
File "/usr/lib/
cls.
File "/usr/lib/
raise ClassInfoError(
ClassInfoError: <type 'instance'
what is interesting:
obj_info = get_obj_info(obj)
File "/usr/lib/
if get_obj_info is called, why stacktrace shows an error in get_cls_info ?
Storm uses a C extension to accelerate some frequently used functions/classes in the code. The get_obj_info() function is one example.
C functions do not have stack frames when unwinding an exception, which is why the traceback skips forward to get_cls_info().