dtrace discuss - Sep 2009 - what is the +hex in c++ stack traces?

What is the hex number after the method, e.g. +0x32f below?

It matches arg0 and I suspect it''s the c++ "this" pointer,
aka hidden
first argument.

I would like to confirm, though.

	Thanks, Joel

---
               XUL`PresShell::ProcessReflowCommands(int)+0x32f
               XUL`PresShell::FlushPendingNotifications(mozFlushType) 
+0x19e
               XUL`PresShell::DidDoReflow(int)+0xeb
               XUL`PresShell::ResizeReflow(int, int)+0x350
               XUL`nsViewManager::SetWindowDimensions(int, int)+0xe3

---
fastest mac firefox!
http://wagerlabs.com

On Wed, Sep 9, 2009 at 1:42 PM, Joel Reymont<joelr1 at gmail.com>
wrote:
> What is the hex number after the method, e.g. +0x32f below?
>
> It matches arg0 and I suspect it''s the c++ "this"
pointer, aka hidden first
> argument.
It matches arg0 to which probe?  These look like function offsets.

Chad
>
> I would like to confirm, though.
>
> ? ? ? ?Thanks, Joel
>
> ---
> ? ? ? ? ? ? ?XUL`PresShell::ProcessReflowCommands(int)+0x32f
> ? ? ? ? ? ? ?XUL`PresShell::FlushPendingNotifications(mozFlushType)+0x19e
> ? ? ? ? ? ? ?XUL`PresShell::DidDoReflow(int)+0xeb
> ? ? ? ? ? ? ?XUL`PresShell::ResizeReflow(int, int)+0x350
> ? ? ? ? ? ? ?XUL`nsViewManager::SetWindowDimensions(int, int)+0xe3
>
> ---
> fastest mac firefox!
> http://wagerlabs.com
>
>
>
>
> _______________________________________________
> dtrace-discuss mailing list
> dtrace-discuss at opensolaris.org
>

On Sep 9, 2009, at 6:56 PM, Chad Mynhier wrote:
> It matches arg0 to which probe?  These look like function offsets.
The pid$target::*:entry one.

---
fastest mac firefox!
http://wagerlabs.com

On Wed, Sep 09, 2009 at 06:42:22PM +0100, Joel Reymont
wrote:
> What is the hex number after the method, e.g. +0x32f below?
> 
> It matches arg0 and I suspect it''s the c++ "this"
pointer, aka hidden
> first argument.
No, it''s far too small for that.  It''s the instruction pointer
offset inside
the function.

Cheers,
- jonathan
> I would like to confirm, though.
> 
> 	Thanks, Joel
> 
> ---
>               XUL`PresShell::ProcessReflowCommands(int)+0x32f
>               XUL`PresShell::FlushPendingNotifications(mozFlushType) 
> +0x19e
>               XUL`PresShell::DidDoReflow(int)+0xeb
>               XUL`PresShell::ResizeReflow(int, int)+0x350
>               XUL`nsViewManager::SetWindowDimensions(int, int)+0xe3
> 
> ---
> fastest mac firefox!
> http://wagerlabs.com
> 
> 
> 
> 
> _______________________________________________
> dtrace-discuss mailing list
> dtrace-discuss at opensolaris.org

Joel Reymont wrote:
>
> What is the hex number after the method, e.g. +0x32f below?
The entries in a stack trace are the addresses of the instructions
that are being executed, expressed as a symbolic address plus an
offset.  The +0x32f you mention is the offset.

If you disassemble the object code, all of the entries except for
the one at the top of the stack should match call instructions.

David
> 
> It matches arg0 and I suspect it''s the c++ "this"
pointer, aka hidden
> first argument.
> 
> I would like to confirm, though.
> 
> 	Thanks, Joel
> 
> ---
>               XUL`PresShell::ProcessReflowCommands(int)+0x32f
>               XUL`PresShell::FlushPendingNotifications(mozFlushType)+0x19e
>               XUL`PresShell::DidDoReflow(int)+0xeb
>               XUL`PresShell::ResizeReflow(int, int)+0x350
>               XUL`nsViewManager::SetWindowDimensions(int, int)+0xe3
> 
> ---
> fastest mac firefox!
> http://wagerlabs.com