[mythtv] [mythtv-commits] Ticket #7011: segfault on startup of mythfrontend
Michael T. Dean
mtdean at thirdcontact.com
Fri Sep 18 02:58:27 UTC 2009
On 09/17/2009 09:28 PM, MythTV wrote:
> Comment:
>
> With a totally empty database, have reproduced (near enough) on Mac OS X:
> {{{
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
> 0x023bc180 in TriggeredConfigurationGroup::Save ()
> }}}
> and Linux:
> {{{
> 2009-09-18 10:54:34.902 Driver error was [2/1146]:
> QMYSQL3: Unable to prepare statement
> Database error was:
> Table 'mythconverg3.settings' doesn't exist
>
> 2009-09-18 10:54:34.903 DB Error (SimpleDBStorage::Save() query):
> Query was:
> SELECT * FROM settings WHERE value = ? AND hostname = ?;
> Bindings were:
> :WHEREHOSTNAME=macaque.ind.tansu.com.au,
> :WHEREVALUE=EndOfRecordingExitPrompt
> No error type from QSqlError? Strange...
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1282136336 (LWP 18050)]
> 0xb66b0f8f in TriggeredConfigurationGroup::Save (this=0x82dd1e0) at
> mythconfiggroups.cpp:521
> 521 configStack->Save();
> #0 0xb66b0f8f in TriggeredConfigurationGroup::Save (this=0x82dd1e0) at
> mythconfiggroups.cpp:521
> #1 0xb66ab7ec in ConfigurationGroup::Save (this=0x8332a38) at
> mythconfiggroups.cpp:99
> #2 0x080840cd in ConfigurationDialog::Save (this=0xbf87f744) at
> ../../libs/libmyth/mythconfigdialogs.h:111
> #3 0x0807a6a8 in WriteDefaults () at main.cpp:640
> #4 0x0807ecc5 in main (argc=1, argv=0xbf87fcb4) at main.cpp:1409
> }}}
> Interestingly, other programs that are supposedly not allowed to upgrade
> schema (like mythav and mythfilldatabase) do not exhibit the error, but
> they are also eventually populating the database, so there is also an
> error in the schema wizard logic?
>
Nigel, FWIW, I have a patch that quiets all the DB errors spamming the
log file on initial DB creation. I'll get it in soon, but need to check
a few things.
You can try running with the initial version of it from
http://misc.thirdcontact.com/MythTV/mythtv-quiet_initial_db_prepare_errors.patch
. Note, however, it does not prevent the attempted DB access--it only
prevents some of the logging (especially the 1000+ messages you get from
all the settings-related access that's now visible since [21875] ).
Therefore, I doubt it will help you (other than making the logs a bit
more readable :).
Mike
More information about the mythtv-dev
mailing list