Ok, I did a little digging in mdb. I'm just going to say up front that I've
NEVER debugged a Kernel, but i am the unix developer for my software company,
so I have a little experience.
>From the stack trace, the last call was:
ffffff0003aed880 xnb_copy_to_peer+0x32(ffffff016a34f000, ffffff013a9368a0)
The first parameter doesn't evaluate to anything based on:
> ffffff016a34f000::dump
\/ 1 2 3 4 5 6 7 8 9 a b c d e f v123456789abcdef
mdb: failed to read data at 0xffffff016a34f000: no mapping for address
Now, the second parameter does evaluate, but to NULL, all 0's
ffffff013a9368a0::dump
\/ 1 2 3 4 5 6 7 8 9 a b c d e f v123456789abcdef
ffffff013a9368a0: 00000000 00000000 00000000 00000000 ................
Is the function xnb_copy_to_peer suppose to assign the second parameter to the
first? Is so, that may explain the problem. The second parameter was NULL, and
if that wasn't check, it could be a NULL pointer exception when it was
attempted to be used.
Like I said, i've only had limited exposure to mdb, so if there are other
commands you guys would like me to run to try and figure this out, let me know.
Thanks
This message posted from opensolaris.org
_______________________________________________
xen-discuss mailing list
[email protected]
