On Thu, Sep 10, 2009 at 11:42:22AM -0700, Rafael Vanoni wrote:
> webrev @ http://cr.opensolaris.org/~rafaelv/mdb-lbolt/
> >
> >Why not move the panic_lbolt() read into mdb_get_lbolt() rather than
> >duplicate it? The existing modules that don't respect panic_lbolt are
> >essentially wrong anyw
Michael (or anybody there). Is it possible to display the state of the
register at a given stack frame? I am interested in "i0", which I
think is the "this" pointer of my c++ program.
I am using mdb to find the address of "this" because I can't make gdb
work with a core file generated by gcore (by
On Wed, Sep 09, 2009 at 11:01:35PM -0700, Rafael Vanoni wrote:
> >>webrev @ http://cr.opensolaris.org/~rafaelv/mdb-lbolt/
Why not move the panic_lbolt() read into mdb_get_lbolt() rather than
duplicate it? The existing modules that don't respect panic_lbolt are
essentially wrong anyway, I think, a
John Levon wrote:
> On Wed, Sep 09, 2009 at 11:01:35PM -0700, Rafael Vanoni wrote:
>
webrev @ http://cr.opensolaris.org/~rafaelv/mdb-lbolt/
>
> Why not move the panic_lbolt() read into mdb_get_lbolt() rather than
> duplicate it? The existing modules that don't respect panic_lbolt are
> essen
On Wed, Sep 09, 2009 at 12:35:33PM +0800, Colin Yi wrote:
> From the above results, We know for the first leak the buffer address
> is 0xff01d710ad18
>
> > *cpqary3_state::walk softstate|::print -at cpqary3_t drvr_replyq
> ff01d51948a0 cpqary3_drvr_replyq_t *drvr_replyq = 0xff01d7f11e
On Wed, Sep 09, 2009 at 03:11:49PM -0700, Rafael Vanoni wrote:
> webrev @ http://cr.opensolaris.org/~rafaelv/mdb-lbolt/
mdb_ks.c:1598
Isn't this wrong for mdb examining crash dumps - it gives the live
kernel's hrtime, not the dump's? Surely you should be looking for
lbolt_debug_ts in the post-mo
