This error description is not very helpful without providing the full log file.
So I can only answer like this:
1.) If you use the 64 bit version, try 32 bit (and vice versa)
2.) Try a previous release it may work for you
3.) Provide the full log file here for deeper analysis
4.) Report what processor architecture you have
Hope that helps...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2023-09-30
Thanks for the quick reply.
I did try 64 bit, 32 bit and 23.08, results were the same.
OK, that is interesting; I see an initialisation of 2 RegEx engines: PCRE2 (which comes from wxWidgets) and sqlite (which comes from wxSQLite). However, these calls should not be related to each other. So I need to figure out what from PCRE2 exactly calls into sqlite3. I assume that some symbols might be mixed...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2023-10-23
That is not an error message but basically an information that the application is falling back to a standard folder. So, since that version works, the reason might actually be a compiler issue with optimising code. If that s the case it will be very hard to track down.
What I can do instead is compiling a version for you that does not use optimisations but also excludes the debugging symbols and therefore becomes smaller. Would that be an option for you?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So, I've managed to make a build accordingly. You can download one of these from the "Files" section:
WebChangeMonitor_23_11-32bit-beta-O0.zip
WebChangeMonitor_23_11-64bit-beta-O0.zip
...depending on your platform.
I've disabled compiler optimisations in this build. Please let me know if these builds show a different behaviour and hopefully) work for you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2023-11-02
I ran both the 32 and 64 bit versions of WCM 23.11 beta-O0. The result was the same as WCM 23.09 Dbg- the message (see attached) appeared and then the app started in what appeared to be the normal manner.
OK, that message would still be expected. However, more important to me is: Does it still crash? Does it work fine? In that case, the reason for the crash is the compiler optimisation, as I would have guessed. Then we found the culprit of your initial request.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2023-11-03
No crash! After the message it appears to be working normally.
Thank you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, thanks for the feedback. In that case, there is nothing I can do except changing the compiler. I do this regularly anyway whenever a new stable GCC compiler is released. So maybe with the next GCC release this bug is gone also when using compiler optimisations.
(Case closed.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I receive the follow error, contained in WebChangeMonitor.RPT, when starting WCM 23.09 64 on a Windows 10 machine.
WebChangeMonitor.exe caused an Illegal Instruction at location 00C22E8A in module WebChangeMonitor.exe.
Any suggestions would be appreciated.
Thank you.
This error description is not very helpful without providing the full log file.
So I can only answer like this:
1.) If you use the 64 bit version, try 32 bit (and vice versa)
2.) Try a previous release it may work for you
3.) Provide the full log file here for deeper analysis
4.) Report what processor architecture you have
Hope that helps...
Thanks for the quick reply.
I did try 64 bit, 32 bit and 23.08, results were the same.
Full log file is attached.
W10 64-bit OS, x64-based processor, Intel Core i7-10510U CPU @ 1.80GHz 2.30 GHz
OK, that is interesting; I see an initialisation of 2 RegEx engines: PCRE2 (which comes from wxWidgets) and sqlite (which comes from wxSQLite). However, these calls should not be related to each other. So I need to figure out what from PCRE2 exactly calls into sqlite3. I assume that some symbols might be mixed...
Therefore, can you please download the debug version of WCM (latest release, ZIP file with an ending Dbg), for example:
https://sourceforge.net/projects/webchangemon/files/Windows/WebChangeMonitor_23_09-64bit-Win7-Dbg.zip/download
(Don't worry that there is Win7 in it - it is Windows 10 compatible.)
Then, run again and attach that full crash log here, please.
Interestingly, the debug version did not crash, it displayed an error message (attached) and then started in what appeared to be the normal manner.
That is not an error message but basically an information that the application is falling back to a standard folder. So, since that version works, the reason might actually be a compiler issue with optimising code. If that s the case it will be very hard to track down.
What I can do instead is compiling a version for you that does not use optimisations but also excludes the debugging symbols and therefore becomes smaller. Would that be an option for you?
Sorry, I wasn't logged in - but this offer is valid.
Sure. I'll give it a try and let you know the results.
Thank you.
So, I've managed to make a build accordingly. You can download one of these from the "Files" section:
...depending on your platform.
I've disabled compiler optimisations in this build. Please let me know if these builds show a different behaviour and hopefully) work for you.
I ran both the 32 and 64 bit versions of WCM 23.11 beta-O0. The result was the same as WCM 23.09 Dbg- the message (see attached) appeared and then the app started in what appeared to be the normal manner.
OK, that message would still be expected. However, more important to me is: Does it still crash? Does it work fine? In that case, the reason for the crash is the compiler optimisation, as I would have guessed. Then we found the culprit of your initial request.
No crash! After the message it appears to be working normally.
Thank you.
OK, thanks for the feedback. In that case, there is nothing I can do except changing the compiler. I do this regularly anyway whenever a new stable GCC compiler is released. So maybe with the next GCC release this bug is gone also when using compiler optimisations.
(Case closed.)