Menu

#36 case in CSndUList::remove_

v1.0_(example)
open
crase (1)
5
2016-01-04
2014-04-29
mingyiliu
No

I use udt library on arm . but i modify the keepalive time in 8s , reduced the thread stack size to 128k . while , udt become fragility ,and i don't know how to handle such issue.
crash :

0 CSndUList::remove_ () from /usr/local/lib/libudt.so

1 CSndUList::pop () from /usr/local/lib/libudt.so

2 CSndQueue::worker () from /usr/local/lib/libudt.so

3 ?? () from /lib/libpthread.so.0

Thank you for your attention .
Doc Gu.

Discussion

  • mingyiliu

    mingyiliu - 2014-04-29

    pin a new case bug:
    in std::less<int>::operator() () from /usr/local/lib/libudt.so
    in std::_Rb_tree<int, std::pair<int="" const,="" CEPollDesc="">, std::_Select1st<std::pair<int const,="" CEPollDesc=""> >, std::less<int>, std::allocator<std::pair<int const,="" CEPollDesc=""> > >::_M_lower_bound () from /usr/local/lib/libudt.so

     
  • Oleh Borysevych

    Oleh Borysevych - 2016-01-04

    Hi.
    We have exactly the same call stack in our crash dump.
    udt is compiled for Windows x64.
    Recently we had several application crashes with Access Violation.
    ExceptionAddress: 000000001d90d333 (udt!CSndUList::remove_+0x0000000000000013)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 0000000000000010
    Attempt to read from address 0000000000000010

    udt!CSndUList::remove_+0x13
    udt!CSndUList::pop+0x89
    udt!CSndQueue::worker+0xb5

    Could not find repro steps or conditions for this crash to reproduce.

    Thank you,
    Oleh

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.