Hi Jasper, you are right.
To avoid SIGSEGV exception, you do not need gdb.exe in the Exclusion List; You only need the project.exe to be on the list. This can be achieved by simply going to the Exclusion List section and pick the file (No need for steps 1 and 2 at all).
I wasted too much effort into making a group list, when it is quite easy just to go directly to the Exclusion List and pick either a file or a folder.
I am always obsessive about making sure, so I went back and checked the 9 combinations of specifying the Exclusion List:
|project \ gdb || Off list|| gdb.exe|| gdb directory|
|Off list || Exception raised || Exception raised || Exception raised |
|project1.exe || OK*|| OK*|| OK*|
|project directory || OK*|| OK*|| OK*|
*I noticed that running debugging build causes Comodo to flash warnings, in the following order:
- 1. Lazarus --> fpc
- 2. fpc --> ppc386
- 3. ppc386 --> windres
- 4. windres --> cpp
- 5. windres --> cmd
- 6. cpp --> cpp
- 7. ppc386 --> content of project1
- 8. gdb --> project1
- 9. lazarus --> project1
I allowed them all, and as a result , Comodo put the following 6 executables into the Protected File and Folder list:
These executables, if I removed them, will cause Comodo to flash warnings again on the next debug run. If I leave them in the Protected Files and Folders list, there was no further warnings from Comodo when I debug.
1. I think we can avoid future SIGSEGV exceptions by making sure that the project you are debugging is in the Exclusion list. You do not need the gdb.exe in the Exclusion List for this purpose. I fully agree with Jasper.
2. I think the 6 executables listed above are the common files that operates when you do a debugging build run, and so it is good to have these in the Protected Files and Folders List.
Thank you again.