It would be useful to find out if this problem is caused by the LIVE555 code
itself, or just by the way that you are using it in your application.
To test this, it would be useful if a "valgrind" enthusiast (aka. a
'valgrinerd' :-) out there could try running "valgrind" on
testRTSPClient rtsp://coooow
(using the unmodified "testRTSPClient" code), and let us know if you see any
signs of bad memory access. (Unfortunately I'm traveling right now, and don't
have access to a computer with "valgrind".)
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
