Community crash test challenge
Hi,
Over the weekend I played a bit with The Hammer 4.0 source and its DLL components to bring it over to DataFlex 2020 in 64 bit mode.
That seems to have worked as it compiles fine to 64 bit and even runs and appears to work well.
Please do _not_ use this preview for editing your projects as I do consider it crash happy at this moment. Just that I do not currently know a way to make it crash for the moment, does not make it stable and reliable.
It is my believe that this is just because I have used it in the happy code path.
So for you available to play with, test and make it crash is the first Hammer 4.0 preview:
[url]https://projects.vdf-guidance.com/attachments/download/180/Hammer4-UNSTABLE-20200221.zip[/url]
If you are able to make it crash in a reproducible way then please let me know here (or via email).
OTOH if you do like to use the Hammer for editing your code then please use the stable Hammer 3 release candidate available at:
[URL]https://projects.vdf-guidance.com/projects/hammer/files[/URL]
(I expect to release another update to that one soonish)
Enjoy!
--
Wil
Re: Community crash test challenge
Wil,
Nice milestone (crash-happy protestations not withstanding)!
Thanks for jumping into the 2020 waters so quickly (and the deep end as well :cool:). Getting many developers involved early helps us (and by extension, the whole community) immensely!
Re: Community crash test challenge
Stephen,
Thanks!
It is no secret that I use The Hammer for writing a lot of my code.
As it is a reasonably sized project with a variety of difficulty levels, it is also a pretty good candidate for experimenting with the new DataFlex 20 features.
Yesterday's head scratcher for the 64 bit rewrite was structure padding alignment :)
So it gives me a good way to practice the techniques I need to be able to use and learn from that.
The bonus is that it benefits the community as well as myself by having another tool you can use.
Bringing the Hammer code to DF20 also forced me to bring the code more up to date.
I might even run DfRefactor over it one of these days :p for that same purpose.
Never did that in the past as it was a good test candidate for DfRefactor, so I actually ran it often, just not committed the changes to the repository.
Forgot to mention in the opening post, but you can compile The Hammer 4.0 UNSTABLE version both in DF19.1 as well as DF20.0.
edit: Also forgot to say that I am amazed at how stable the DataFlex 20 Tech Preview already is at this moment. REALLY well done DAW team!
--
Wil
Re: Community crash test challenge
Hi,
Also updated the Hammer 4 with a new version.
Quite frankly I found many ways to crash The Hammer 4 when running in 64 bit.
This version -hopefully- is a lot more stable. I still would not recommend you to use it as a daily driver (use The Hammer3 for that)
There's new DLLs again.
Also all changes that happened in The Hammer 3 have been merged here as well (see my last 2 posts here: [URL]https://support.dataaccess.com/Forums/showthread.php?64400-The-Hammer-3-Release-Candidate-1[/URL] )
Besides that some Hammer4 specific patches have been made for DataFlex 2020 support only.
Such as structure padding, fixes on Windows events to use ULongPtr instead of integer for the wparam/lparam variables, corrections on the structures to match the 64 bit scintilla version (not everything that was docced was how it really was in source ha!)
Changing a workspace does now save that setting again to the registry (yeah I rewrote that old "SET_FOREIGN_PROFILE_STRING" logic that Vincent urged me to change)
The .hws file was not read/written correctly at all, it messed up completely.
More details on what has changed can be found here:
[URL]https://projects.vdf-guidance.com/projects/hammer/repository[/URL]
Download at: [URL]https://projects.vdf-guidance.com/attachments/download/180/Hammer4-UNSTABLE-20200221.zip[/URL]
cheers!
--
Wil
2 Attachment(s)
Re: Community crash test challenge
[QUOTE=wila;352645]Hi,
Also updated the Hammer 4 with a new version.
Wil[/QUOTE]
Below is exactly the bug I reported on Saturday, only today it manifested itself in whatever version of H3 I have, after a clean boot, then starting H419.1 and H420x64.
[ATTACH=CONFIG]13499[/ATTACH]
[ATTACH=CONFIG]13500[/ATTACH]
Re: Community crash test challenge
Re: Community crash test challenge
Hi Dave,
In your email you mentioned that you only got this error one time after the initial start.
Do you really unzip into that folder : "Hammer3-development-beta-20190326" ?
If not, could it be that the hammer was the current workspace when you start up and it was pointing to that folder?
Just wondering.. from the looks of it, the file does actually exist and it looks like it is even in the hammer3.cfg list, so the linker should have embedded it in the binary.
Making this even more curious.
--
Wil
Re: Community crash test challenge
[QUOTE=wila;352679]Hi Dave,
In your email you mentioned that you only got this error one time after the initial start.
Do you really unzip into that folder : "Hammer3-development-beta-20190326" ?
If not, could it be that the hammer was the current workspace when you start up and it was pointing to that folder?
Just wondering.. from the looks of it, the file does actually exist and it looks like it is even in the hammer3.cfg list, so the linker should have embedded it in the binary.
Making this even more curious.
--
Wil[/QUOTE]
1. Yes, second run of H4 at least is usually perfect.
more later, I've something to finish. Also I want to make sure I didn't bend anything during the install.