Re: [Live-devel] How to contribute code?

2010-06-21 Thread Ross Finlayson
I don't use any revision control system myself.  When I'm developing 
this code, I use exactly two commands: "emacs" and "make".


Each source code release - in "tar.gz" form - is less than 500 kBytes 
in size.  These days, that's not a significant amount of data to 
download in order to get the latest revision, and any bandwidth 
savings obtained by downloading from a revision control system 
instead would be insignificant.  And people should not be using any 
version of the code other than the latest one, because that's all 
that we support.


I suspect that the real reason why some people want to use a revision 
control system is that they want to easily update to the latest 
version of the code after they've made custom modifications to it 
(i.e., without losing their modifications).  I'm sorry, but this is 
something that I explicitly want to discourage.  People *should not* 
be making modifications to the released "LIVE555 Streaming Media" 
code (i.e., inside the "live" directory).  Instead, they should be 
leaving that directory as it is, and instead putting their own code 
in a separate directory (using subclassing, if necessary).


If there are parts of the code that make it difficult for people to 
customize via subclassing - e.g., some class members that should be 
"protected:" instead of "private:", then please let us know.

--

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


[Live-devel] openRTSP segfault on max osx

2010-06-21 Thread Kenneth Ljungh
Hi

running openRTSP -q -w 704 -h 576 rtsp://192.168.0.101/axis-media/media.amp 
>test.mov  & 
and sending kill -HUP sometimes ends with a segfault. This is with live555 
2010.06.18 but I didn't see this with 2010.04.09

Regards

Kenneth

crash log:

Code Type:   X86-64 (Native)
Parent Process:  bash [17661]

Date/Time:   2010-06-21 20:55:29.059 +0200
OS Version:  Mac OS X 10.6.4 (10F569)
Report Version:  6

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x
Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
0   libSystem.B.dylib   0x7fe00800 __memcpy + 96
1   libSystem.B.dylib   0x7fff846e51ae __sfvwrite + 429
2   libSystem.B.dylib   0x7fff84736579 fwrite + 128
3   openRTSP0x00010002253f 
SubsessionIOState::useFrame(SubsessionBuffer&) + 529
4   openRTSP0x000100022f4a 
SubsessionIOState::afterGettingFrame(unsigned int, timeval) + 512
5   openRTSP0x000100022fd9 
QuickTimeFileSink::afterGettingFrame(void*, unsigned int, unsigned int, 
timeval, unsigned int) + 75
6   openRTSP0x00014ab7 
FramedSource::afterGetting(FramedSource*) + 59
7   openRTSP0x0001e056 
MultiFramedRTPSource::doGetNextFrame1() + 532
8   openRTSP0x0001e34c 
MultiFramedRTPSource::networkReadHandler(MultiFramedRTPSource*, int) + 670
9   openRTSP0x00010002b8a8 
BasicTaskScheduler::SingleStep(unsigned int) + 666
10  openRTSP0x00010002acd8 
BasicTaskScheduler0::doEventLoop(char*) + 38
11  openRTSP0x000100018630 
RTSPClient::teardownMediaSession(MediaSession&) + 68
12  openRTSP0x000116e6 
clientTearDownSession(Medium*, MediaSession*) + 26
13  openRTSP0x00012428 tearDownStreams() + 
28
14  openRTSP0x000124b4 shutdown(int) + 138
15  openRTSP0x000124f5 
signalHandlerShutdown(int) + 34
16  libSystem.B.dylib   0x7fff8473335a _sigtramp + 26
17  libSystem.B.dylib   0x7fff84716dce select$DARWIN_EXTSN 
+ 10
18  openRTSP0x00010002b708 
BasicTaskScheduler::SingleStep(unsigned int) + 250
19  openRTSP0x00010002acd8 
BasicTaskScheduler0::doEventLoop(char*) + 38
20  openRTSP0x00014344 main + 5841
21  openRTSP0x000116c4 start + 52



___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel


Re: [Live-devel] How to contribute code?

2010-06-21 Thread Jeremy Noring
On Fri, Jun 18, 2010 at 7:18 AM, Ross Finlayson wrote:

> I was also not able to find any public git or svn repository for live555.
>> Could
>> you consider to make one?
>>
>
> No.  We make available - and provide support for - the most recent version
> of the code only.
>

Just because you use source control doesn't mean you have to support any
random release of the code.  Almost no open source projects I know function
this way; there are clear releases and supported versions.  Is there some
other reason you're opposed to public source code?  It's really difficult
not having a history of changes made (and a changelog is a poor substitute
for source control history), or being able to roll back the library to a
previous version to locate regression.

My $0.02: if you've gone this long without source control, then I don't
expect you're about to change, but you should really reconsider this
decision at some point.
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel