ReactOS 0.4.14: Crash after calling DoDragDrop

[Zorn]

I am in the process of programming a replacement for the incompletely developed program winefile, which is included in Wine and ReactOS (c:\reactos\system32\winefile.exe. I use the C programming language (C 89 variant) with Win32 API and I make sure to develop it in a way that it is compilable with mingw as well as with mingw-w64 with (almost) no compiler warnings. I was successful at this until I started programming drag and drop. Program with drag and drop support works with Windows 10 and Wine 6.03, but when I run it under ReactOs 0.4.14 (Virtualbox) and test drag and drop with it and my program calls the win32 API function DoDragDrop, then ReactOS crashes (ignores all mouse movements and keystrokes), at the latest shortly afterwards when I close my program again. It seems to be extremely difficult to call DoDragDrop(...) in C without crashing ReactOS 0.4.14 (the crash can also happen a minute later after DoDragDrop(...) has been called. I have also tried to program IDataObject, IDropSource and IDropTarget with very little code and functionality in my drag and drop module to see if it works better then, but this only delays the crash of ReactOS. Do you have any idea how I could manage to program drag and drop in C in such a way that ReactOs does not crash?

[Zorn]

I have just solved the problem by fixing a memory allocation bug (too less bytes allocated).

[rodrigueza]

How can you systematically isolate the problem to determine whether it lies within your implementation of the IDataObject, IDropSource, and IDropTarget interfaces, or if it is related to ReactOS's handling of the Win32 API functions?

[dizt3mp3r]

Join the Mattermost chat using your login details from this forum, if your query is related to ReactOS development then post in the development channel. If it is ReactOS-related then post onto Town Square, if not strictly related to ReactOS, then post on Off Topic.

I'm sure you will receive some interest if you choose to join the ReactOS community on Mattermost. https://chat.reactos.org/landing#/reactos/

[cubauks]

How did you track down the memory allocation bug? I've been struggling with similar issues in ReactOS, and any tips on debugging crashes like this would be super helpful!