wxWidgets Discussion Forum

That is exactly what happened, initially, but after some fiddling with the data supplied to MFCDemo, I finally got the server to accept the data :D Thank you for sticking with this issue; it gave me enough information to keep trying with the original MFCDemo and now I can take on my 'real' applicati...

The real problem seems to be, that whichever version I happened to pick fails the Unit tests for SMTP & HTTP delivery, so all of my trials for that sort of result is likely to fail in any case. As well, I have no real idea how I might debug that part of the project - the crash sender. Haven't found ...

does $file_root end up as server home directory relative or a regular Win OS file path?
Neither works for me

Any special setup/code required at the server end?
I have copied the PHP file found with the crashRpt code to the server htdocs\crashRpt\
I am working with xampp 7.13.10 on a separate PC on my LAN

FWIW, just an update and to record the bit of progress. When compiling and debugging the MFCDemo, I have run into an assert issue regarding the hardwired dbghelp dll version when working on Win 10 & the latest MSVC 2019 updates. The code (from wherever I got it), has 6.1.11 hard coded as the version...

FWIW: If you use VS anyway, i recommend crashrpt, much more powerful: http://crashrpt.sourceforge.net/ Finally got crashrpt installed, compiled and linked into one of my smallish test programs. It seems that the project is now abandon-ware and since my work with this code thus far has raised a numb...

same issue with MSVC 2015 & 2017
Will look into crashrpt - had downloaded it some time ago, but never spent the time to test it and replace my existing code. Looks like now is the time to do so
Thank you all

3.1.3 (32-bit) debug version shows the same problem, I'm afraid

All libraries are built by myself, using the same IDE as for the samples All testing dome under the up-to-date Win 10 OS with an up-to-date MSVC community edition IDE the full stack trace at the time of the crash below - with the Exception message: Exception thrown at 0x76F341CA (kernel32.dll) in de...

After trying to use debug reporting & having issues with my own code - which follows the example in samples, I tried the sample project, but it will not run at all under MSVC 2019 IDE. Using any of the report options, it crashes with Exception thrown at 0x76F341CA (kernel32.dll) in debugrpt.exe: 0xC...

@DM & PB
Thank you both for the clarifications

so the queue is really used mainly for feedback to the secondary thread and one still would need to use an event to initiate any action in the main thread, with possibly extra information via the queue?

I know this is an old thread, but rather than start over I would like to ask where in the main app one would wait for feedback from the secondary thread via the message queue?
Via events or in OnIdle, OnUiUpdate?
TIA

That may well be the best option
For my current apps, I am really only interested in getting a thumbnail and checking for minimal compliance with the TIFF standards,
Will have to see if libtiff will give me that much. Though it would be preferable not to have to treat TIFFs as a special case.

After implementing the sub-classed log code, I can intercept the error messages produced by calls to wxLogError & wxLogWarning by code deep inside wxImage:: LoadFile() but the calls to the intercept logic are delayed by way too much time to be usable in the code after the call to LoadFile() returns....