Project

General

Profile

Bug #5554

kmdb can't trace stacks that begin within itself

Added by Rich Lowe almost 6 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
mdb - modular debugger
Start date:
2015-01-22
Due date:
% Done:

100%

Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:

Description

Robert reported that after #5132, kmdb can't trace a stack out of itself, believing the %fp to be invalid. That's because kmdb runs in a logical separate piece of stack, which is much higher than the normal thread stack space

History

#1

Updated by Electric Monk over 5 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

git commit 32b5e9f0cda85eef94eb578dd053e155df43fed3

commit  32b5e9f0cda85eef94eb578dd053e155df43fed3
Author: Richard Lowe <richlowe@richlowe.net>
Date:   2015-01-29T16:05:43.000Z

    5554 kmdb can't trace stacks that begin within itself
    Reviewed by: Josef 'Jeff' Sipek <josef.sipek@nexenta.com>
    Reviewed by: Alex Reece <alex@delphix.com>
    Approved by: Robert Mustacchi <rm@joyent.com>

Also available in: Atom PDF