Search results

Ah - didn't see you'd debugged further, but yeah you got it. There's a field in the ExFrame structure (well, actually 0x28 before the base address of the frame in x86) that holds the base address for the parameter values, and on the Immediate window's frame, it's just null - that'd usually be...

Interesting! Found the issue. It seems the weird ".0_#ImmMod#_._ImmedProc" frame that you get from the immediate window doesn't actually have a base address for it's parameter values, but it does actually have 3 parameters, which is.. Really odd. So it can get the parameter names and types for...

I figured it was something along those lines. Don't worry, didn't take it personally. I do find it odd that .bas isn't an allowed file type for attachments though..!

I haven't worked on local variables much. Values should be possible, fairly easy even - their names would be an ordeal though, Access never loads them in a compiled MDE. I'd have to read the compressed streams that the VBE stores, which I don't think would be feasible in VBA itself. I have...

Oh - yeah. That's just a trick to make LongPtr "work" in VBA6 (so long as it's a 4 byte value, it's fine) so I don't have to duplicate tonnes of code. It isn't valid in VBA7 but that doesn't matter, since the conditional compilation ignores it. You get the same with any stuff declared as PtrSafe...

Hm. What was wrong with the CopyMemory definition?

Ahh, that makes more sense. Interesting that it leaves the rest of the callstack intact even if you manually intervene! Thanks for the clarification.

Understood - have made changes myself. We OK with the mentions of other communities / figures that do more openly take things apart? I.e., Sandsprite and Ionescu.

Well that's even more interesting. I'm guessing it must be related to the breakpoint then..? But I can't seem to replicate it myself. Odd! Edit: Yeah, if I call something from the immediate window I do get that frame in the result. Running "Form_Form1.Command0_Click" in the immediate window...

Huh - that "ImmedProc" part I believe to be related to the immediate window? I didn't know it had an object name or procedure name though - I honestly thought it would just break my code entirely. Interesting! I wouldve thought if you used the immediate window to run the code though, it would...

Posted this on a few different forums, but Access is my home so figured I should post it here, too. I've been working on a project called VBAStack, which was initially a project that used Microsoft's published symbols for VBE7.dll to call internal functions and read the callstack. Recently...