This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(182.40000000000003, 87%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
Hi guys,
I've a large visual c++ project migrated from vs2013 to Visual studio 2022. All went fine for almost of the binaries except for one of them that crashed soon after started. Debugging it, it seems that due to heap problems some HWND belonging to some buttons of a CFomView become null and the view crashes during the first InitialUpdate routine.
I know that to troubleshoot such a problem could be a nightmare, so I ask suggestions about what kind of tools I could use to understand and fix the problem..
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 64%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EF%3C/text%3E%3C/svg%3E)
And what in your OnInitialUpdate is crashing ? One difference between old VS and new VS is that CDocument is loading before loading CView, of course, its not the only difference. But making debugging, you'll be able to sucessfully migrate to VS2022.
I come from 1 week debugging without success... It seems that a pWnd-> was nullptr when the form dispatches the WM_INITIALUPDATE message to its descendants..
So the window is not created at that point ... go and do debug to some level up.
I think that what I see is a side effect.. The window is created, in fact if I move some code of may class, the error moves from a control to another one. Moreover, the same code works correctly if I enable some internal compiler conditions that have no relationship with windows controls or Cdocument/view procedure..
The situation changed if I chage the "Struct member Alignement" under code generation section of the compiler. Moving from "default" to 1 or 4 hides the problem and the application can finally start. Now, any idea on how to find where this setting is working better than "default"?
I think that the problem is solved. One of the external library used a directive #pragma pack (1) before an union, but no #pragma pack() were used to restore the default packaging.. This causes a misalignment that in my case means "crash".. I fixed the code of the external library and no need to change the default structure alignment of the project.
The question could be why this error raised only moving the project to VS2022, but I suppose that the answer should go deeper inside the compilation process..
All the best!