Project

General

Profile

Actions

Bug #680

closed

pisensor crashes

Added by Hammel over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Immediate
Assignee:
Category:
Software
Target version:
Start date:
25 Sep 2018
Due date:
% Done:

100%

Estimated time:
Severity:
01 - Critical

Description

There are three bugs in pisensors:
  1. (non-crash) The background color is light gray instead of what the theme color is.
  2. pisensors doesn't start from appmgr or perhaps starts but crashes immediately.
  3. pisensors crashes if you run it manually and then click on a cell entry that has nothing in it. Here is the backtrace for this one.
    (gdb) bt
    #0  strlen () at ../sysdeps/arm/armv6t2/strlen.S:85
    #1  0x76552798 in __GI___strdup (s=0x0) at strdup.c:41
    #2  0x000152f8 in dbModifyEntry (entry=0x0, delete=0, state=1) at db.c:326
    #3  0x000129ec in toggleState (entry=0x0) at pisensors.c:287
    #4  0x00012b64 in button_press (widget=0x58950, event=0x88680, user_data=0x4)
        at pisensors.c:334
    #5  0x76d32b3c in _gtk_marshal_BOOLEAN__BOXED () from /usr/lib/libgtk-x11-2.0.so.0
    #6  0x76828cf8 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
    #7  0x7683960c in ?? () from /usr/lib/libgobject-2.0.so.0
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
    

The last one is probably just not checking that the click doesn't map to a dbEntry.
The second one requires running pisensors -v3 -l/tmp/pisensors.log from it's launcher XML config.
The first one is just a cairo thing - check what the media player launcher does or maybe just make it black.


Related issues

Related to Monitor - Feature #645: Create a prototype app for monitoring devicesClosedHammel17 Jul 2018

Actions
Actions

Also available in: Atom PDF