[mythtv] Ticket #10724: lossless transcode "'Unrecoverable error"
Michael T. Dean
mtdean at thirdcontact.com
Mon May 14 18:13:49 UTC 2012
On 05/14/2012 01:48 PM, Steven Adeff wrote:
> On Mon, May 14, 2012 at 1:38 PM,<noreply at mythtv.org> wrote:
>> #10724: lossless transcode "'Unrecoverable error"
>> --------------------------------------------+------------------------------
>> Reporter: Steven Adeff<adeffs.mythtv@…> | Owner:
>> Type: Bug Report - General | Status:
>> Priority: minor | infoneeded_new
>> Component: MythTV - Mythtranscode | Milestone: unknown
>> Severity: medium | Version: 0.25-fixes
>> Keywords: | Resolution:
>> | Ticket locked: 0
>> --------------------------------------------+------------------------------
>> Changes (by beirdo):
>>
>> * status: new => infoneeded_new
>>
>>
>> Comment:
>>
>> Where's the backtrace? That gdb.txt file has just the headers from gdb
>> starting up. Also, what exact version?
> odd, I ran mythtranscode through gdb, which I was under the impression
> from the wiki would then collect the data for the application as it
> ran?
> perhaps it's not "crashing" out, and just exiting cleanly? is there a
> way to collect the data of why it's error'ing?
You'll want to set a breakpoint at the place where it's issuing the
"Unrecoverable error" message.
http://sourceware.org/gdb/current/onlinedocs/gdb/Set-Breaks.html#Set-Breaks
easiest way is to add:
break mythfrontend/main.cpp:123
to your gdbcommands.txt file (right after the "break qFatal" line would
be a good place). You can get the actual file name and line number of
the log message directly from the log output. Note that the filename
(when specified as a "relative" file name, as above) will match any file
with the same trailing components--so, I didn't need to say
"programs/mythfrontend/main.cpp" because "mythfrontend/main.cpp" is
unique enough, and if I just said, "main.cpp", it would match main.cpp,
regardless of application I run).
Mike
More information about the mythtv-dev
mailing list