Print a backtrace if the SDT(9) stub gets called so that there's at least
some hope of figuring out how it happened. Suggested by: rstone MFC after: 1 week
This commit is contained in:
parent
82dd802622
commit
19ec16208e
@ -27,6 +27,7 @@
|
||||
|
||||
#include <sys/param.h>
|
||||
#include <sys/systm.h>
|
||||
#include <sys/kdb.h>
|
||||
#include <sys/sdt.h>
|
||||
|
||||
SDT_PROVIDER_DEFINE(sdt);
|
||||
@ -47,5 +48,6 @@ sdt_probe_stub(uint32_t id, uintptr_t arg0, uintptr_t arg1,
|
||||
uintptr_t arg2, uintptr_t arg3, uintptr_t arg4)
|
||||
{
|
||||
|
||||
printf("sdt_probe_stub: Why did this get called?\n");
|
||||
printf("sdt_probe_stub: unexpectedly called\n");
|
||||
kdb_backtrace();
|
||||
}
|
||||
|
Loading…
x
Reference in New Issue
Block a user