Todd Lipcon has submitted this change and it was merged. Change subject: pstack_watcher: set a limit on backtrace depth ......................................................................
pstack_watcher: set a limit on backtrace depth On RHEL 6.8, pstack_watcher-test times out fairly reliably, with a 'gdb' process left spinning 100% CPU. Some googling found a report of a similar spinning GDB while taking a backtrace[1]. This report suggests setting a backtrace limit -- apparently the spinning is due to gdb getting in some infinite loop trying to walk the stack with insufficient/incorrect debug info. This patch sets such a limit. I verified on a box which was reliably reproducing the timeout that it is now fixed. [1] https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/434168 Change-Id: Ide46209256fd4ced6b08065c2ae3c0046de49565 Reviewed-on: http://gerrit.cloudera.org:8080/6658 Reviewed-by: Adar Dembo <[email protected]> Reviewed-by: Mike Percy <[email protected]> Tested-by: Kudu Jenkins --- M src/kudu/util/pstack_watcher.cc 1 file changed, 10 insertions(+), 0 deletions(-) Approvals: Mike Percy: Looks good to me, approved Adar Dembo: Looks good to me, approved Kudu Jenkins: Verified -- To view, visit http://gerrit.cloudera.org:8080/6658 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-MessageType: merged Gerrit-Change-Id: Ide46209256fd4ced6b08065c2ae3c0046de49565 Gerrit-PatchSet: 3 Gerrit-Project: kudu Gerrit-Branch: master Gerrit-Owner: Todd Lipcon <[email protected]> Gerrit-Reviewer: Adar Dembo <[email protected]> Gerrit-Reviewer: Kudu Jenkins Gerrit-Reviewer: Mike Percy <[email protected]> Gerrit-Reviewer: Todd Lipcon <[email protected]>
