Opened 15 years ago
Closed 14 years ago
#6544 closed defect (invalid)
DB Connection related segfault
Reported by: | stuartm | Owned by: | Isaac Richards |
---|---|---|---|
Priority: | major | Milestone: | 0.22 |
Component: | MythTV - General | Version: | head |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
Seems to stem from an attempt to use a dead connection, few lines preceeding the segfault in the logs are more interesting than the backtrace itself IMHO
Attachments (1)
Change History (3)
Changed 15 years ago by
Attachment: | db_connection_segfault.txt added |
---|
comment:2 Changed 14 years ago by
Resolution: | → invalid |
---|---|
Status: | new → closed |
From the backtrace it looks like the Qt bug where ~QSqlQuery which eventually calls mysql_next_result() in QMYSQLResult with a NULL handle. This only happens with a MYSQL_VERSION_ID >= 40100 when we have an invalid DB connection.
Note: This does appear to be fixed upstream though I don't know when, see
http://qt.gitorious.org/qt/qt/blobs/master/src/sql/drivers/mysql/qsql_mysql.cpp
On line 420 they have added two null pointer checks.
Note: See
TracTickets for help on using
tickets.
Log and Backtrace