Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
WINE Debugging
Configure Enterprise Architect to debug under WINE
Step |
Action |
See also |
|---|---|---|
|
1 |
At the command line, run $ winecfg. |
|
|
2 |
Set the library overrides for dbghelp to (native, builtin), and accept the warning about overriding this DLL. |
|
|
3 |
Set dbghelp to native by using winecfg. |
|
|
4 |
Copy the application source code plus executable(s) to your bottle. The path must be the same as the compiled version; that is:
If Windows source = C:\Source\SampleApp, under Crossover it must be C:\Source\SampleApp |
|
|
5 |
Copy any Side-By-Side assemblies that are used by the application. |
Access Violation Exceptions
Due to the manner in which WINE handles direct drawing and access to DIB data, an additional option is provided on the drop-down menu on the Debug window toolbar to ignore or process access violation exceptions thrown when your program directly accesses DIB data.
Select this option to catch genuine (unexpected) access violations; deselect it to ignore expected violations.
As the debugger cannot distinguish between expected and unexpected violations, you might have to use trial and error to capture and inspect genuine program crashes.
Notes
- If WINE crashes, the back traces might not be correct
- If you are using MFC remember to copy the debug side-by-side assemblies to the C:\window\winsxs directory
- To add a windows path to WINE, modify the Registry entry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment
