Boost unit test framework and the "system" system call under Linux.

Hello, I'm a bit new to Boost, so please don't throw rocks at me if this sounds stupid. I have a simple module that allows to wrap an external command execution using "system()". It returns a result that depends on the exit code. I want to unit test this with boost test, as I do for other modules. Unfortunately, it seems that the framework catches the signal of the child exit if it exits with a non-zero exit code. So that the unit test is aborted, which is not what I want. It seems the Execution Monitor is the solution to my problem. Is it ? How can I use it to prevent Boost from catching every signal ? Thanks in advance, -- Mathieu

Avila Mathieu
Unfortunately, it seems that the framework catches the signal of the child exit if it exits with a non-zero exit code. So that the unit test is aborted, which is not what I want.
This is in a queue to be fixed.
It seems the Execution Monitor is the solution to my problem. Is it ? How can I use it to prevent Boost from catching every signal ?
You can disable all the signals using catch_system_errors=no Genandiy
participants (2)
-
Avila Mathieu
-
Gennadiy Rozental