prod success state succeed ready submit queued has queue printer install ok - install complete success state
l
The first thing you'll notice is that the version number is "1.0". It should be 1.1, as the supportprod part is broken. If you look carefully you'll see "priority = -1", which means there's nothing higher than it in the queue. I suspect this happened when the connection broke.
Next you'll see "l = 1" and "l = 2". This means the application is done.
The last thing you should see is a return code of -1, which means there was a problem. In this case we have an access violation.
We can't really use a stack trace in this case, as it might not be there when we're done. That's why we have to go to the message boxes. Message boxes may not be easy to read for some, but you can always make them bigger or get a magnifying glass.
OK, here's the first part of the message:
Error 21000068: Access violation reading location 0x07B8C7FC. A system error has occurred. If this problem persists, report it to Microsoft.
This is the "System Error" part. So there's some problem somewhere, but it's not affecting our code yet.
Next we have a string that tells us what the problem is. In this case it says "Access violation reading location 0x07B8C7FC". The problem is in the address 07B8C7FC. Let's look up that value.
Back in Visual Basic we have:
? clsDebug
? DumpStack()
? DumpThis()
? RunThis()
This takes us to a method called DumpThis. This opens up a message box. You can see that this method has two parameters. One is int, which is the access violation value, and the other is string. There's also a line that says "l = 0". Let's skip ahead to the next line and look at it.
? l & = 0 & " 0x" & Hex(Mid(cstr(&), 2))
The DumpStack method will dump the contents of a structure or class to a message box. When you first call it, it does not return anything.
So we can go to the end of 3125841983

Items