• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 313
  • Last Modified:

What is Param#1, Param#2 in Dr.Watson Log

Hi,
I have few questions about the Stack Back Trace section of Dr.Watson Log. here is the sample of the Dr.Watson log I am trying to analyse.

*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
0728fcc4 77664a12 00000084 000006a4 00000001 00000004 ntdll!NtWaitForSingleObject
0728fdec 776b9f5f 000006a5 0728fe64 00000000 00000000 msafd!<nosymbols>
0728fe3c 75615392 000006a5 0728fe64 00000000 00000000 ws2_32!select
0728ff84 7800248d 7561a218 506e6570 656b6361 004b0310 wsnmp32!SnmpSetPort
0728ffb8 77f04ede 004b0310 506e6570 656b6361 004b0310 !beginthreadex
0728ffec 00000000 00000000 00000000 00000000 00000000 kernel32!lstrcmpiW
00000000 00000000 00000000 00000000 00000000 00000000 ObjectManager!<nosymbols>


My Questions are:
1). Does the values indicated in the Param#1, Param#2, etc are actual values or the Address of the memory location where my variables are stored?

2). If these are address to the variable, how I can find out the actual value I have passed?

3). Even though my method takes only two params, why the other to params are also filled with some value? What are those values? For ex. SnmpSetPort takes only to params, it has values 7561a218, 506e6570, 656b6361, 004b0310 for Param#1, 2, 3 &4 respectively.

0
Thangs
Asked:
Thangs
  • 2
1 Solution
 
jkrCommented:
You cannot tell that without knowing whether your code is passing values or pointers - thus you need the symbol files. I suggest reading http://msdn.microsoft.com/msdnmag/issues/02/06/Bugslayer/default.aspx for a guide to crash dump analysis using DrWatson logs.
0
 
ThangsAuthor Commented:
jkr,
I am passing only the values. I have noticed that when I pass value say "5", still it is giving me a big 32 number. What am I missing here?
0
 
jkrCommented:
It could well be that the compiler passes the values in a CPU register - what you are seeing in the log is the stack, though.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now