[Guy Harris <gharris@xxxxxxxxx>]

On Sun, Nov 17, 2002 at 10:29:47AM +1100, Ronnie Sahlberg wrote:
> dissect_rpc_opaque_data(tvbuff * 0x02873d74, int 132, _GNode * 0x028c3124,
> int 5344, int 0, char * * 0x00000000) line 618 + 38 bytes
> dissect_rpc_data(tvbuff * 0x02873d74, _GNode * 0x028c3124, int 5344, int
> 128) line 675 + 25 bytes
> ...
> Why does offset change from 128 to 132 between the call to
> dissect_rpc_data() and dissect_rpc_opaque_data() ?
> offset is not changed inside dissect_rpc_data() until after the call to
> dissect_rpc_opaque_data() has
> completed, and thus dissect_rpc_opaque_data() should have the same value
> passed to it.
> Is this some weird sideeffect of the debugger on windows?  must be.

If the debugger shows the second argument to "dissect_rpc_opaque_data()"
by fetching the current value of that argument, it'll report 132 rather
than 128 if the current statement is after the "offset += 4".