i looking @ backtrace in gdb, , looks cluttered because of calls made standard library , boost. eg. see boost::bind
, std::allocator
on call stack, , several other similar calls standard library or boost.
i think find helpful have backtrace show me functions explicitly defined in program. better yet, further if configure backtrace command show or hide std
, boost
calls , when need them.
any idea how hide boost
call stack altogether or configure backtrace turn boost logging on , off?
there no built-in way this.
it can done, though, writing python "frame filter" drops frames don't care see. isn't particularly hard do, requires writing bit of python code using gdb python api.
Comments
Post a Comment