On Sun, 2 Oct 2005, Frank Albrecht wrote:

> >     What does a gdb backtrace look show?  Perhaps knowing where the
> >     fault is happening will provide an idea what area to investigate.
> 
> Puh, I don't know how to do that.

        gdb yourprogram
        run program_args

        when the fault happens type 'where':

        where

        That wasn't so hard, was it? :-)

> My idea was to do ltrace because of library related problem:

        That's a good start.  One problem with tracing system calls is that
        a program doesn't fault at a "system call" (such as read(), write()
        or pthread_create()) but further on.

>  $ ltrace streamer -t 0:30 -o movie.mov -f yv12 -F mono16
>  pthread_cond_init(0x0806a6a8, 0, 0, 0, 0x401a3104) = 0
>  malloc(960)                                      = 0x08064e70
>  malloc(1264)                                     = 0x08065238
>  pthread_mutex_init(0x08065238, 0, 0, 0, 1)       = 0
>  pthread_mutex_init(0x080656c0, 0, 0x400388af, 0x08065238, 16) = 0
>  pthread_cond_init(0x080656d8, 0, 0x400388af, 0x08065238, 16) = 0
>  pthread_create(0x08065708, 0, 0x080529d0, 0x08065238, 0x080655a4) = 0
>  pthread_mutex_init(0x080653b0, 0, 0xbffff318, 0x08065238, 16) = 0
>  pthread_cond_init(0x080653c8, 0, 0xbffff318, 0x08065238, 16) = 0
>  pthread_create(0x080653f8, 0, 0x080527c0, 0x08065238, 0x08065294) = 0
>  --- SIGSEGV (Segmentation fault) ---
>  +++ killed by SIGSEGV +++

        It could be a threading issue - but all we know at this point is
        that the program faulted sometime _after_ creating a thread.

        instead of ltrace try something like this:

        gdb streamer
        run -t 0:30 -o movie.mov -f yv12 -F mono16

        when the program faults use either the 'where' or 'bt' (backtrace) - 
        they are the same command, just different names.

> Is it possible to use mencoder or ffmpeg for capturing for
> mjpegtools? I couldn't figure out how to create an input
> satifying lav2yuv/mpeg2.

        Perhaps others who capture to mjpeg can help with some ideas - but
        I thought 'lavrec' was the usual method used to capture mjpeg data.

        I have not had success with ffmpeg and MJPEG data - on a big endian
        system (PPC) a solid green screen, and on little endian system (AMD,
        Intel) only one of the fields appears.

        I think 'lavrec' would be your best choice - perhaps Bernhard will
        have time to help you with some suggestions.

        Cheers,
        Steven



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Mjpeg-users mailing list
Mjpeg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mjpeg-users

Reply via email to