Need help with state-threads?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

ossrs
487 Stars 220 Forks 53 Commits 7 Opened issues

Description

Light-weight thread library, coroutine or c++ goroutine , patched for SRS.

Services available

!
?

Need anything else?

Contributors list

state-threads

Fork from http://sourceforge.net/projects/state-threads, patched for SRS.

See: https://github.com/ossrs/state-threads/blob/srs/README

For original ST without any changes, checkout the ST master branch.

Usage

Get code:

git clone https://github.com/ossrs/state-threads.git st-1.9 &&
git checkout -b srs origin/srs

For Linux:

make linux-debug EXTRA_CFLAGS="-DMD_HAVE_EPOLL"

For OSX:

make darwin-debug EXTRA_CFLAGS="-DMD_HAVE_KQUEUE"

Linux with valgrind:

make linux-debug EXTRA_CFLAGS="-DMD_VALGRIND"

Remark: User must install valgrind, for instance, in centos6

sudo yum install -y valgrind valgrind-devel
.

Linux with valgrind and epoll:

make linux-debug EXTRA_CFLAGS="-DMD_HAVE_EPOLL -DMD_VALGRIND"

For OSX, user must specifies the valgrind header files:

make darwin-debug EXTRA_CFLAGS="-DMD_HAVE_KQUEUE -DMD_VALGRIND -I/usr/local/include"

Remark: Latest OSX does not support ST, please use docker to run ST.

Branch SRS

The branch srs will be patched the following patches:

Valgrind

How to debug with gdb under valgrind, read valgrind manual.

About startup parameters, read valgrind cli.

Important cli options:

  1. --undef-value-errors= [default: yes]
    , Controls whether Memcheck reports uses of undefined value errors. Set this to no if you don't want to see undefined value errors. It also has the side effect of speeding up Memcheck somewhat.
  2. --leak-check= [default: summary]
    , When enabled, search for memory leaks when the client program finishes. If set to summary, it says how many leaks occurred. If set to full or yes, each individual leak will be shown in detail and/or counted as an error, as specified by the options
    --show-leak-kinds
    and
    --errors-for-leak-kinds
    .
  3. --track-origins= [default: no]
    , Controls whether Memcheck tracks the origin of uninitialised values. By default, it does not, which means that although it can tell you that an uninitialised value is being used in a dangerous way, it cannot tell you where the uninitialised value came from. This often makes it difficult to track down the root problem.
  4. --show-reachable= , --show-possibly-lost=
    , to show the using memory.

Docs & Analysis

  • Introduction: http://ossrs.github.io/state-threads/docs/st.html
  • API reference: http://ossrs.github.io/state-threads/docs/reference.html
  • Programming notes: http://ossrs.github.io/state-threads/docs/notes.html

  • About setjmp and longjmp, read setjmp.

  • About the stack structure, read stack

  • About asm code comments, read #91d530e.

  • About the scheduler, read #13-scheduler.

  • About the IO event system, read #13-IO.

  • Code analysis, please read #15.

Winlin 2016

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.