EXC_BAD_ACCESS (BUG)

91 Views Asked by At
    ClientState: 1
ClientState: 2
ClientState: 3
ClientState: 4
ClientState: 5
ClientState: 6
received server window size: 2500000
received peer bandwidth limit: 2500000 type: 2
Received invoke
pktId: 1
received invoke _result
tracked command: connect
ClientState: 7
received unknown packet type: 0x00
Received invoke
pktId: 2
received invoke _result
tracked command: releaseStream
Received invoke
pktId: 3
received invoke _result
tracked command: FCPublish
Received invoke
pktId: 4
received invoke _result
tracked command: createStream
ClientState: 8
Received invoke
pktId: 0

received invoke onStatus And then the app crashes and stops inside RTMPSession::parseStatusCode - most of the times strncpy inside the do-while loop leads to an EXC_BAD_ACCESS exception, sometimes a few lines later. and

int ret = ((val[2]&0xff)) | ((val[1]&0xff) << 8) | ((val[0]&0xff)<<16) ; -------- bad excess code

Do you have any ideas on how this can be solved?

Additional information: we are using Red5 on server side.

0

There are 0 best solutions below