Weird debugger behavior with events

[Russell Johnson <russell.johnson@kratosdefense.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1281 bytes --]

Hello,

 

I have a simple test app with two EVL threads (basics shown below). When I
run the app outside of a debugger, both threads run as expected with no
in-band switches or errors from the EVL core. However, when I run in the
debugger, I am seeing evl_timedwait_event returns -1 when the app is started
and then eventually it finally returns -110 (ETIMEDOUT). It makes it very
hard to debug. I would expect it to run like it does outside of the debugger
- thread 1 should just keep re-calling timedwait as it should keep timing
out. The other weird thing is that if I run thread 1 in the debugger without
thread 2 running, then it will work fine. Any ideas?

 

EVL Thread 1 does the following:

        evl_lock_mutex(&mutex);

        for (size_t i = 0; i < 1000; i++)

        {

            struct timespec tnow;

            evl_read_clock(EVL_CLOCK_MONOTONIC, &tnow);

            tnow.tv_sec += 1;

            int rv = evl_timedwait_event(&event, &mutex, &tnow);

            if ((rv < 0) && (rv != -ETIMEDOUT))

            {

                evl_printf("-1 error ocurred\n");

            }

        }

        evl_unlock_mutex(&mutex);

 

EVL Thread 2 does the following:

    while(true)

    {

        evl_usleep(1000);

    }

 

 

Thanks,

Russell

 

 

 


[-- Attachment #1.2: Type: text/html, Size: 4461 bytes --]

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 6759 bytes --]