Re: [Check-users] gdb, fork() and side effects

[Branden A. <b.m...@gm...>]

You can tell Check to run only a specific suite or test case using the
environment variables CK_RUN_CASE and CK_RUN_SUITE. You can also mark a
test case with a tag and run only tests which match that tag using the
environment variable CK_INCLUDE_TAGS. See the documentation here
<https://libcheck.github.io/check/doc/check_html/check_7.html#Environment-Variable-Reference>
for
both of those.

Hope it helps.

- Branden

On Thu, Mar 8, 2018 at 10:26 PM, Igor Fontana <ro...@sk...>
wrote:

> EHLO
>
> i just hit a segfault on my tests and stated debugging...
>
> first i tried to run it inside gdb, but then it becomes a mess because
> it forks liek 300 times.
>
> then i tried to CK_FORK=no, but it makes good tests crash because they
> rely on fork() to isolate side effects.
>
> then i tried to manage teh forks inside gdb but its impossible.
>
> then i started to think about checking my fixtures and managing side
> effects myself, but i fear this is gonna be quite a lot of work and
> very error prone.
>
> finally i thought i could run just teh problematic unit test on
> CK_FORK=no, but i couldnt find a way to run just a _single unit test_,
> and to make things worse, its a loop test.
>
> so before refactoring more mistakes into my code, i thought it would
> be worth to ask here. could somebody give me a light on this matter?
> please?
>
> thank you! <3
>
> --
> Igor
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Check-users mailing list
> Che...@li...
> https://lists.sourceforge.net/lists/listinfo/check-users
>