[MPlayer-users] Segmentation fault in pre5

[D Richard Felker III]

On Sun, Oct 17, 2004 at 01:17:32PM +0100, Martin Simmons wrote:
> > > > anything that happens at a random location each time you run a program
> > > > is _definitely_ heat-caused. mencoder doesn't read from /dev/urandom
> > > > and pick what to do based on the results. the results of each run are
> > > > entirely deterministic and won't vary from one to another.
> > > 
> > > There is plenty of other non deterministic problems that are not caused by
> > > heat or urandom.  Particular cases that I've seen (not in mencoder yet):
> > > 
> > > - timing-related issues for interaction between threads or processes
> > not threaded. this is one reason threaded apps suck.
> 
> Yes, I know mencoder is not using threads (though it does link with libpthread
> so let's hope nothing calls those fns :-).

they'll be used for tv-cap and perhaps for some windows-binary codecs.
nothing else.

> The other issue is processes -- mencoder calls gettimeofday() like there is no
> tomorrow, so anything else running on the machine could cause subtle changes
> in the behaviour of time-critical code.

this is just to report performance on the statusline. it has nothing
to do with the actual encoding.

> > > - OS bugs (causing registers to be corrupted)
> > never seen this myself...maybe windows? :o
> 
> Solaris and VxWorks.

ahh... ;)

rich