Opened 7 years ago

Closed 7 years ago

#9894 closed Bug Report - General (fixed)

Backend SIGSEGV processing flags

Reported by: Ian Dall <ian@…> Owned by: beirdo
Priority: minor Milestone: 0.25
Component: MythTV - General Version: Unspecified
Severity: medium Keywords:
Cc: Ticket locked: no


Version: v0.25pre-2556-gc12e7d7-dirty

I get SIGSEGV due to gCoreContext->HasGUI() called with null gCoreContext. I only see this with the patch in #9893 applied.

A simple fix is to test for gCoreContext non-null. A patch is supplied. With this patch, AND the patch in #9893 applied, mythbackend starts reliably. I'm not necessarilly climing that this is the right fix. Maybe gCoreContext should be established earlier.

Attachments (2)

mythsystem.cpp.diff (566 bytes) - added by Ian Dall <ian@…> 7 years ago.
Patch to not dereference NULL gCoreContext
gcorecontext.gdb (1.2 KB) - added by Ian Dall <ian@…> 7 years ago.
gdb session log

Download all attachments as: .zip

Change History (5)

Changed 7 years ago by Ian Dall <ian@…>

Patch to not dereference NULL gCoreContext

Changed 7 years ago by Ian Dall <ian@…>

gdb session log

comment:1 Changed 7 years ago by beirdo

  • Owner set to beirdo
  • Status changed from new to assigned

Please follow the same steps as #9893, and report back.

comment:2 Changed 7 years ago by beirdo

  • Status changed from assigned to infoneeded

comment:3 Changed 7 years ago by Github

  • Milestone changed from unknown to 0.25
  • Resolution set to fixed
  • Status changed from infoneeded to closed

Setup http proxy after the gCoreContext is initialized

Fixes #9893. Fixes #9894.

The setHttpProxy() uses myth_system to ping the proxy. However, myth_system requires that gCoreContext be valid for proper use. Therefore, move the proxy setup to after where we setup the context.

Branch: master Changeset: df8b987413106d47701a6c8ff04185b411d1a5b5

Add Comment

Modify Ticket

as closed The owner will remain beirdo.
The resolution will be deleted. Next status will be 'new'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.