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

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

I do not think that there is a mechanism for running a specific test in
isolation, only a specific suite or case. The only advice I can think of is
to set gdb to follow forks and set breakpoints to stop on specific
conditions, for example if the loop in a given test is a specific value.

https://stackoverflow.com/questions/14390256/gdb-break-if-variable-equal-value

- Branden

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

> > 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 for
> both of
> > those.
>
> yes, but they wont let me pick just a single unit test inside teh
> suite/case, right?
>
> what i needed was something liek CK_RUN_TEST and CK_RUN_TEST_I, which
> would allow to restrict even further. or perhaps something shorter,
> liek CK_RUN_ID, which would uniquely identify a unit inside a case
> inside a suite.
>
> in my test case i have some common data and a huge table of operation
> parameters to try. some of those parameters run just fine and some
> segfault. so if i run teh whole test case it is still problematic to
> either CK_FORK=no, because of side effects, or gdb with fork().
>
> sorry if im asking too much! and thank you again for teh quick response! <3
>
> --
> Igor
>