Re: Theora got extreamly slow (Makefile.am was changed)

"R. P. Janaka" <[email protected]>
Newsgroups gmane.comp.multimedia.ogg.theora.devel
Message-ID <[email protected]>
Thanks for your advices. now I am checking the program for fixing the bug.

Once I make a modification to the *Makefile.am*, I got the proper
functionality in expected way. But the problem is that functionality will
not happened at always, it changed *randomly* (*some times work properly,
some times half work, some time one part is work etc.*).

the change i did with the Makefile.am is..


AM_CFLAGS = -O2 -Wall $(DEFS) $(INCS)
instead of
CFLAGS = -O2 -Wall $(DEFS) $(INCS)


Can any one give reasons for this behavior.....? Why this random behavior,
why it is working in unpredictable way...?





On Wed, Apr 23, 2008 at 8:30 PM, <[email protected]> wrote:

> On Wed, Apr 23, 2008 at 9:34 AM, R. P. Janaka <[email protected]> wrote:
> > In my application there are two threads. One is the theora encoder the
> other
> > is a bandwidth measuring program.
> >
> > Both of them are working properly when they are separated. (theora is
> > obviously working properly, bandwidth measuring component also working
> > properly)
> >
> > So this problem is occurred when both these are joined (encoder is the
> main
> > thread, bandwidth measurer is the child thread)
>
> This is the basic definition of a 'concurrency bug'.  Just because
> they work seperately doesn't mean there aren't substantial bugs that
> will pop out when two threads work together.  Why do you think this
> has anything to do with the Makefile?
>
> Turning on optimization will often make a buggy program behave
> differently because it changes the relative timings between threads.
>
> > So i think that the problem is with my makefile. Please can anyone help
> me
> > to find the problem
>
> I would be very surprised if the makefile has anything to do with it.
> Designing concurrent programs (threads especially) is perhaps the
> single hardest thing in software engineering.  Debugging even very
> simple multithreaded programs can be maddening because the simple act
> of turning on debugging or turning off optimization can drastically
> change how a bug behaves.
>
> I'd love to help, but it would drive me insane....
>
> Monty
>



-- 
Regards,
R. P. Janaka

_______________________________________________
theora-dev mailing list
[email protected]
http://lists.xiph.org/mailman/listinfo/theora-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.