Opened 19 years ago

Closed 19 years ago

Last modified 19 years ago

#2222 closed defect (fixed)

Segfault with mythbackend. SVN 10904

Reported by: neilsym.mythtv@… Owned by: Anduin Withers
Priority: minor Milestone: unknown
Component: mythtv Version:
Severity: medium Keywords:
Cc: Ticket locked: no

Description

I upgraded from a SVN build of about two weeks ago. I get a segfault immediately after I start mythbackend. I've created a debug build, and will attach a log and backtrace.

Attachments (2)

gdb.txt​ (32.6 KB ) - added by neilsym.mythtv@… 19 years ago.
myth.log​ (5.3 KB ) - added by neilsym.mythtv@… 19 years ago.

Download all attachments as: .zip

Change History (7)

by neilsym.mythtv@…, 19 years ago

Attachment: gdb.txt​ added

by neilsym.mythtv@…, 19 years ago

Attachment: myth.log​ added

comment:1 by henrik.lilljebjorn AT home.se, 19 years ago

I also get this segfault with SVN 10907

comment:2 by neilsym.mythtv@…, 19 years ago

I should have said before: I'm using Suse 10.0 x86-64 on an Athlon 64. I see the segfault every time I try to start mythbackend.

comment:3 by Anduin Withers, 19 years ago

Owner: changed from Isaac Richards to Anduin Withers

comment:4 by Anduin Withers, 19 years ago

Resolution: → fixed
Status: new → closed

(In [10919]) Closes #2222

You don't get to step forward and erase, not reliably.

comment:5 by danielk, 19 years ago

(In [10934]) Refs #2222. Make ChannelUtil::EliminateDuplicateChanNum() a little bit safer (a little add-on to awithers' major fix in [10919]).

rkulagow is experiencing a segfault due to the DBChannel::channum QString reference count being off, this fixes is one of the unsafe assignments...

Note: See TracTickets for help on using tickets.