C#
An object-oriented and type-safe programming language that has its roots in the C family of languages and includes support for component-oriented programming.
11,156 questions
user32.dll!UserCallWinProcCheckWow()
![](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(163.2, 94%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJY%3C/text%3E%3C/svg%3E)
Jin Yang
20
Reputation points
My MFC embed WPF, and sometimes I want to show a WPF dialog, it will crash. I find below difference, and want to know when execute the two functions.
- there is not parameter in the crashed call stack: user32.dll!UserCallWinProcCheckWow()
- there are parameters in the working call stack: **user32.dll!UserCallWinProcCheckWow(struct _ACTIVATION_CONTEXT ,__int64 ()(struct tagWND *,unsigned int,unsigned __int64,int64),struct HWND ,enum _WM_VALUE,unsigned __int64,__int64,void ,int)
work well call stack:
crashed call stack:
C#
C++
C++
A high-level, general-purpose programming language, created as an extension of the C programming language, that has object-oriented, generic, and functional features in addition to facilities for low-level memory manipulation.
3,808 questions
{count} votes
-
![](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(201.6, 57.00000000000001%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMY%3C/text%3E%3C/svg%3E)
Minxin Yu 12,341 Reputation points Microsoft Vendor2024-12-17T01:30:16.9433333+00:00 It is hard to identify the problem with call stack. Can you share some steps and minimal code example to help us reproduce the issue?
-
Jin Yang 20 Reputation points
2024-12-17T02:01:55.2633333+00:00 A case is that MFC work thread call a C# API to show a modal WPF dialog while MFC CMenu::TrackPopupMenu() is popup.
- C# API use Invoke to show the modal dialog from mainthread :
- Dispatcher.FromThread(MainThread).Invoke(action, null);
- Dispatcher.FromThread(MainThread).Invoke(action, null);
I feel there is something wrong when operate both MFC view and WPF UI, the main thread how to handle the message from MFC and WPF.
- C# API use Invoke to show the modal dialog from mainthread :
-
Minxin Yu 12,341 Reputation points Microsoft Vendor
2024-12-17T03:25:43.6733333+00:00 I can't reproduce the problem based on your description.
-
Jin Yang 20 Reputation points
2024-12-17T05:51:42.3766667+00:00 Yes, I also can't repeat it. Only appeared twice。
I found the difference in the callstack(you can check the previous image). I don't know in which case will cause the user32.dll call the overloaded function.
- the crash's callstack called user32.dll!UserCallWinProcCheckWow(),
- but the working callstack is user32.dll!UserCallWinProcCheckWow(struct _ACTIVATION_CONTEXT **,__int64 (****)(struct tagWND *,unsigned int,unsigned __int64,**int64),struct HWND ,enum _WM_VALUE,unsigned __int64,__int64,void ,int)
-
Minxin Yu 12,341 Reputation points Microsoft Vendor
2024-12-18T02:10:39.13+00:00 The only available doc I've found is for CallWindowProc:
int (FAR WINAPI * FARPROC) ()
In C, the FARPROC declaration indicates a callback function that has an unspecified parameter list.
Sign in to comment
Sign in to answer