dtrace discuss - Jul 2009 - Interpreting addresses in dtrace stack

Hi, 

   I have a simple dtrace script running when I start a xen guest viz.  dtrace
-n mac_register:entry{stack();}

   When I start a xen guest with xm start, I see a hardware address as caller of
mac_register:


bash-3.2# xm start guest3

  3  24844               mac_register:entry
              0xfffffffff7dd502f
              genunix`devi_attach+0x88
              genunix`attach_node+0x121
              genunix`i_ndi_config_node+0xe4
              genunix`i_ddi_attachchild+0x6e
              genunix`devi_attach_node+0xfe
              genunix`config_immediate_children+0xf5
              genunix`devi_config_common+0xa6
              genunix`mt_config_thread+0x5d
              unix`thread_start+0x8

How do I figure out which function calls the mac_register routine?

Also, is dtrace stack output showing hardware address a bug? Since am 
just starting guest domain (and the guest is running successfully), I 
don''t think the module invoking mag_register got unloaded before dtrace
could map the hardware address with symbol and print it out. dtrace 
stack should have shown the correct caller thus...


TIA,
Shri