i wish to thank the people at the gnu tools for letting me use this software and some of the other tools they provide. and special thanks to the crack finder team for making this software. and especially i would like to thank my beta tester david zempel for his help with the documentation. and to the many many people who have written me emails with questions and suggestions for new features. thank you.
what i'd like to do with this project is to get a few (10 at least) people with delphi 5 (or newer) to run down the memory locations, look up the corresponding function, and then see how we can combine this information with other information about the delphi object-oriented framework. anybody with delphi 5 or newer should be able to find the memory location, and get an idea of what might be happening.
like i said before, i have enough of a grasp of the delphi object-oriented framework that i can write code that does what i want. but if i can find a way to get a little more insight into what is going on, that'd be great.
there isnt anything like that in delphi 5. the stacktrace class is in the system unit. so you must compile with -dstacktrace to get it. (use -dstacktrace -fno-code for optimizing your code, because it makes this a lot harder.)
yet the one thing i dont like about delphi is the lack of high level generics. i can understand that its a very powerful language and that code is much more readable and maintainable, when you use a type-safe language like c#, but i just cant live with the lack of generics in delphi. there are ways to work around that and i dont want to mention them in this post, because they are not the point of the first post of the series. i just want to show how to do this. 3d9ccd7d82