Opened 12 years ago
Closed 12 years ago
#11043 closed Bug Report - Crash (Duplicate)
SEGV From mythlogserver When It Shuts Itself Down
Reported by: | Owned by: | beirdo | |
---|---|---|---|
Priority: | trivial | Milestone: | unknown |
Component: | MythTV - Mythlogserver | Version: | Master Head |
Severity: | low | Keywords: | |
Cc: | Ticket locked: | no |
Description
Similar to #10924, however,
--daemon was used logserver was started automatically (by the FE) backtrace isn't exactly the same
I have 5 more core files/backtraces available. The addresses in the failures are 0x0, 0x20 and 0x30.
To Duplicate:
Verify no MythTV processes are running On a remote FE, Start mythfrontend, and exit via the menu Wait for mythlogserver to timeout
Attachments (3)
Change History (8)
Changed 12 years ago by
Attachment: | mythlogserver.20120825192452.5058.log added |
---|
Changed 12 years ago by
Attachment: | gdb-mythlogserver-5058.txt added |
---|
Changed 12 years ago by
Attachment: | version.txt added |
---|
comment:1 Changed 12 years ago by
Milestone: | unknown → 0.26 |
---|---|
Priority: | minor → major |
comment:2 Changed 12 years ago by
Milestone: | 0.26 → unknown |
---|---|
Priority: | major → trivial |
Severity: | medium → low |
Status: | new → assigned |
This is a nuisance, but in no way is it blocking anything. I will continue to work on this, but it will almost assuredly not be fixed for 0.26
comment:3 Changed 12 years ago by
Reported upstream at https://github.com/jonnydee/nzmqt/issues/8.
Note: See
TracTickets for help on using
tickets.
v0.26-rc-2-ge55b5b1