Opened 18 years ago
Closed 18 years ago
Last modified 18 years ago
#2222 closed defect (fixed)
Segfault with mythbackend. SVN 10904
Reported by: | 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)
Change History (7)
comment:1 Changed 18 years ago by
comment:2 Changed 18 years ago by
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 Changed 18 years ago by
Owner: | changed from Isaac Richards to Anduin Withers |
---|
comment:4 Changed 18 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:5 Changed 18 years ago by
(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...
I also get this segfault with SVN 10907