Difference between revisions of "Talk:Multithreaded Application Tutorial"
From Free Pascal wiki
Jump to navigationJump to search (fpc_popaddrstack()) |
|||
| Line 7: | Line 7: | ||
I do not use "try-except" and "try-finally" blocks in my code and I don't need exception handling. | I do not use "try-except" and "try-finally" blocks in my code and I don't need exception handling. | ||
My question is: '''How to supress the fpc_popaddrstack() or (better) all routines in unit "except.inc"?''' (any directive to disable it) | My question is: '''How to supress the fpc_popaddrstack() or (better) all routines in unit "except.inc"?''' (any directive to disable it) | ||
| + | |||
I will be very grateful for a solution to my problem. | I will be very grateful for a solution to my problem. | ||
Revision as of 01:36, 16 February 2014
fpc_popaddrstack()
I want to use FPC to compile my WinApi multi-threaded application but after compilation and running I often receive SIGSEGV error. After debugging, the segmentation fault is ALWAYS in function "fpc_popaddrstack()".
The application uses hooks and CreateRemoteThread. Thus additional calls to "fpc_popaddrstack()" must not be made. The trick described in that article will not work properly. These calls shall be disabled.
I do not use "try-except" and "try-finally" blocks in my code and I don't need exception handling. My question is: How to supress the fpc_popaddrstack() or (better) all routines in unit "except.inc"? (any directive to disable it)
I will be very grateful for a solution to my problem.
