Stack dump format ?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Stack dump format ?

Chris Uppal-3
What's the story on the stack dump format in D6 ?  Is the IP number hex/decimal
variability thing sorted out ?

I tried Ghoul on a manually-produced stack dump, and it seemed to work OK, more
or less.  Looking at the dump, it seemed likely that all the IP numbers were in
decimal (Ghoul currently default to expecting hex in that context, IIRC).

TIA.

    -- chris


Reply | Threaded
Open this post in threaded view
|

Re: Stack dump format ?

Blair McGlashan
"Chris Uppal" <[hidden email]> wrote in message
news:[hidden email]...

> What's the story on the stack dump format in D6 ?  Is the IP number
> hex/decimal
> variability thing sorted out ?
>
> I tried Ghoul on a manually-produced stack dump, and it seemed to work OK,
> more
> or less.  Looking at the dump, it seemed likely that all the IP numbers
> were in
> decimal (Ghoul currently default to expecting hex in that context, IIRC).
>
> TIA.

I didn't think anything had been done to explicitly sort that problem out,
but its possible that it was addressed when some other changes were made.
Now is the time to change it, so if you find a problem please do raise a
defect. Hex would be better, but given time constraints (and the cosmetic
nature) its probably not something I'd change unless there is some other
reason to change the code.

Regards

Blair


Reply | Threaded
Open this post in threaded view
|

Re: Stack dump format ?

Chris Uppal-3
Blair,

> I didn't think anything had been done to explicitly sort that problem out,
> but its possible that it was addressed when some other changes were made.
> Now is the time to change it, so if you find a problem please do raise a
> defect.

I'll raise a bug report, but I don't know whether the bug has already been
fixed.  It was always an intermittent and unpredictable misreporting of the
IPs.  I don't think I've ever seen it happen on this machine, but I have seen
stack dumps posted to the main NG that exhibit the problem.

> Hex would be better, but given time constraints (and the cosmetic
> nature) its probably not something I'd change unless there is some other
> reason to change the code.

Well, I wouldn't call it all /that/ cosmetic myself.  But I'll raise a bug
report and it's obviously up to you how you prioritise it.  But if you check
the code and find that the bug is already fixed them please let me know.

    -- chris


Reply | Threaded
Open this post in threaded view
|

Re: Stack dump format ?

Schwab,Wilhelm K
Blair,

> I'll raise a bug report, but I don't know whether the bug has already been
> fixed.  It was always an intermittent and unpredictable misreporting of the
> IPs.  I don't think I've ever seen it happen on this machine, but I have seen
> stack dumps posted to the main NG that exhibit the problem.

Could the problem be in part due to patching of the VM and/or compiler?
  There is a 5.1 hot fix for handling of temps.  AFAIK, you never
updated the 5.1 installers, which is a shame because the new libraries
make a huge difference for the usefulness of the debugger.  I have a
separate InnoSetup based installer that I am happy to make available if
it is of any use.  FWIW, I have been surprised at how many times I have
needed it.

The bottom line is that I wonder whether the patched libraries might use
a different IP representation than the installed libraries????


>>Hex would be better, but given time constraints (and the cosmetic
>>nature) its probably not something I'd change unless there is some other
>>reason to change the code.

Anything you can do to help Ghoul would be appreciated; it's a great
concept.

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]