On Monday 23 January 2006 19:09, Jim Westfall wrote: > Steve Adeff <[EMAIL PROTECTED]> wrote [01.23.06]: > > > here's the log output from a crash, it occured while in edit mode: > > > > > > 2006-01-21 10:13:14.099 59520 bytes free on soundcard > > > 2006-01-21 10:13:14.099 WriteAudio: Preparing 6144 bytes (1536 frames) > > > 2006-01-21 10:13:14.107 54912 bytes free on soundcard > > > 2006-01-21 10:13:14.115 56448 bytes free on soundcard > > > 2006-01-21 10:13:14.126 58432 bytes free on soundcard > > > 2006-01-21 10:13:14.126 NVP: ClearAfterSeek() > > > 2006-01-21 10:13:14.126 VideoOutputXv: ClearAfterSeek() > > > 2006-01-21 10:13:14.126 VideoBuffers::DiscardFrames(0): > > > AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA > > > 2006-01-21 10:13:14.126 VideoBuffers::DiscardFrames(0): > > > AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA -- done > > > 2006-01-21 10:13:14.127 NVP: new commBreakIter = 4 @ frame 43142 > > > 2006-01-21 10:13:14.127 detectInterlace(Detect Scan, Interlaced Scan, > > > 29.97, 480) ->Interlaced Scan > > > 2006-01-21 10:13:14.127 Interlaced: Interlaced Scan video_height: 480 > > > fps: 29.97 > > > > > > the crashes seem to be related to deinterlacing except that I don't > > > have deinterlacing turned on.... > > > > could this be a 64bit kernel issue? > > http://www.mythtv.org/docs/mythtv-HOWTO-22.html#ss22.2 > > jim
already put up a GDB backtrace in trac of playback, but am unsure as to how to go about it for mythbackend recording. should I just run gdb mythbackend -x gdbcommands start recording something via firewire? then when should I CTRL-C to create the backtrace? -- Steve _______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
