Opened 16 years ago
Closed 15 years ago
Last modified 14 years ago
#5832 closed defect (wontfix)
segmentation fault when scanning channels for DVB
Reported by: | Owned by: | danielk | |
---|---|---|---|
Priority: | major | Milestone: | 0.21.1 |
Component: | dvb | Version: | 0.21-fixes |
Severity: | high | Keywords: | dvb segmentation fault scanning scan |
Cc: | Ticket locked: | yes |
Description
mythtv-setup is unable to scan for DVB-C channels - and causes a segmentation fault. Steps:
- Close mythbackend.
- Start mythtv-setup
- Configure DVB-C card and some video-source (no grabber)
- Goto Input connections - and assosiate the video-source.
- Select "Full Scan of Existing Transports" or Full Scan (I ised: Freq: 143000000, Symbolrate: 6875000)
Hit "Next" and mythtv-setup will cause a segmentation fault
Attachments (1)
Change History (7)
comment:1 Changed 15 years ago by
comment:2 Changed 15 years ago by
I'm running Ubuntu 8.10, with mythtv 0.21+fixes 18722. I recompiled with debug symbols.
The attached gdb output is generated after scanning a known transport for channels (using DVB-C). Scan works perfect, updates are processed, but the usual 'Finish' screen crashes/segfaults.
More information needed?
comment:3 Changed 15 years ago by
I think this problem is related to multiple core cpu.
With "taskset -c 0 mythtv-setup" (running only on the first cpu core) dvb scan ends without errors.
Note: It appear both on DVB-S and DVB-T. Note2: At the moment I cannot reproduce it...
comment:4 Changed 15 years ago by
Status: | new → assigned |
---|
comment:5 Changed 15 years ago by
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
This segfault doesn't happen with the new scanner in the mythtv-channel-scan branch, and I've tried unsuccessfully to fix it with the old scanner one too many times, so this is a wontfix. As soon as the issues with the new scanner wrt to DVB-X are resolved we'll replace the current non-thread-safe scanner with the new thread-safe channel scanner...
comment:7 Changed 14 years ago by
Ticket locked: | set |
---|
I can confirm. I'll try to debug.