• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[SOLVED] Triggering generic_switch leads to segfault
#3
(10-08-2019, 09:34 PM)curlymo Wrote: I have no issues when testing it here in my local setup. Can you post a debug log as described in the manual?
https://manual.pilight.org/development/debugging.html

Hi!

I've tested to switch one clarus-switch without the generic-switch and rule. This works fine.

With the gerneric-switch i get the following gdb-log:
Code:
[Oct 09 11:53:03:310459] DEBUG: socket write succeeded: {"origin":"update","type":1,"uuid":"0000-b8-27-eb-cd7a82","devices":["Diele"],"values":{"timestamp":1570621983,"state":"on"}}

[Oct 09 11:53:03:310546] DEBUG: broadcasted: {"origin":"update","type":1,"uuid":"0000-b8-27-eb-cd7a82","devices":["Diele"],"values":{"timestamp":1570621983,"state":"on"}}
[Oct 09 11:53:03:310745] DEBUG: socket write succeeded: {"origin":"sender","protocol":"generic_switch","message":{"id":99,"state":"on"},"repeat":1,"uuid":"0000-b8-27-eb-cd7a82"}

[Oct 09 11:53:03:310796] DEBUG: broadcasted: {"origin":"sender","protocol":"generic_switch","message":{"id":99,"state":"on"},"repeat":1,"uuid":"0000-b8-27-eb-cd7a82"}
[Oct 09 11:53:03:313887] DEBUG: lua thread on state #1
[Oct 09 11:53:03:314121] INFO: executed rule: DieleAn
[Oct 09 11:53:03:314164] DEBUG: lua thread on state #0
[Oct 09 11:53:03:314178] DEBUG: rule #48 DieleAn was parsed in 0.000899 seconds
[Oct 09 11:53:03:314381] DEBUG: rule #49 DieleAus was parsed in 0.000076 seconds
[Oct 09 11:53:03:315115] DEBUG: **** RAW CODE ****
180 540 540 180 180 540 180 540 180 540 540 180 180 540 540 180 180 540 180 540 180 540 540 180 180 540 540 180 180 540 540 180 180 540 180 540 540 180 540 180 180 540 180 540 540 180 540 180 180 6120
[Oct 09 11:53:03:315270] DEBUG: **** RAW CODE ****
[Oct 09 11:53:03:316321] DEBUG: **** RAW CODE ****
[Oct 09 11:53:03:316413] DEBUG: lua async on state #0
180 540 540 180 180 540 180 540 180 540 540 180 180 540 540 180 180 540 180 540 180 540 540 180 180 540 540 180 180 540 540 180 540 180 540 180 180 540 180 540 180 540 180 540 540 180 540 180 180 6120
[Oct 09 11:53:03:316503] DEBUG: **** RAW CODE ****
[Oct 09 11:53:03:316910] DEBUG: socket write succeeded: {"origin":"update","type":1,"uuid":"0000-b8-27-eb-cd7a82","devices":["SteckdoseRund1"],"values":{"timestamp":1570621983,"state":"on"}}

[Oct 09 11:53:03:317032] DEBUG: broadcasted: {"origin":"update","type":1,"uuid":"0000-b8-27-eb-cd7a82","devices":["SteckdoseRund1"],"values":{"timestamp":1570621983,"state":"on"}}
[Oct 09 11:53:03:317227] DEBUG: socket write succeeded: {"origin":"sender","protocol":"clarus_switch","message":{"id":"A3","unit":18,"state":"on"},"repeat":1,"uuid":"0000-b8-27-eb-cd7a82"}

[Oct 09 11:53:03:317318] DEBUG: broadcasted: {"origin":"sender","protocol":"clarus_switch","message":{"id":"A3","unit":18,"state":"on"},"repeat":1,"uuid":"0000-b8-27-eb-cd7a82"}
[Oct 09 11:53:03:318123] DEBUG: lua async on state #0
[Oct 09 11:53:03:318582] DEBUG: socket write succeeded: {"origin":"update","type":1,"uuid":"0000-b8-27-eb-cd7a82","devices":["SteckdoseRund2"],"values":{"timestamp":1570621983,"state":"on"}}

[Oct 09 11:53:03:318661] DEBUG: broadcasted: {"origin":"update","type":1,"uuid":"0000-b8-27-eb-cd7a82","devices":["SteckdoseRund2"],"values":{"timestamp":1570621983,"state":"on"}}
[Oct 09 11:53:03:318874] DEBUG: socket write succeeded: {"origin":"sender","protocol":"clarus_switch","message":{"id":"B3","unit":18,"state":"on"},"repeat":1,"uuid":"0000-b8-27-eb-cd7a82"}

[Oct 09 11:53:03:318927] DEBUG: broadcasted: {"origin":"sender","protocol":"clarus_switch","message":{"id":"B3","unit":18,"state":"on"},"repeat":1,"uuid":"0000-b8-27-eb-cd7a82"}
[Oct 09 11:53:03:416259] DEBUG: lua timer on state #0
[Oct 09 11:53:03:663302] DEBUG: lua timer on state #0

Thread 1 "pilight-daemon" received signal SIGSEGV, Segmentation fault.
strlen () at ../sysdeps/arm/armv6/strlen.S:26
26    ../sysdeps/arm/armv6/strlen.S: Datei oder Verzeichnis nicht gefunden.


(gdb) backtrace
#0  strlen () at ../sysdeps/arm/armv6/strlen.S:26
#1  0x76585ba8 in lua_getfield ()
  from /usr/lib/arm-linux-gnueabihf/libluajit-5.1.so.2
#2  0x7682cd28 in ?? () from /usr/local/lib/libpilight.so
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Uli
 
Reply
  


Messages In This Thread
RE: Shelly device - by curlymo - 10-08-2019, 09:34 PM
RE: Shelly device - by Ulrich.Arnold - 10-09-2019, 01:18 PM

Possibly Related Threads...
Thread Author Replies Views Last Post
  ][solved]Segfault when retrieving big chunked http message Niek 21 7,765 11-29-2018, 03:17 PM
Last Post: curlymo
  http code 301 causes segfault Niek 3 3,717 08-14-2018, 06:57 PM
Last Post: curlymo
  Long label text causes segfault Niek 10 2,169 06-29-2018, 02:18 PM
Last Post: Niek
  [Solved] config.json not updated Niek 6 2,173 12-31-2017, 03:19 PM
Last Post: curlymo
  [Solved] callback not executing when dns lookup fails Niek 1 1,070 10-08-2017, 11:44 AM
Last Post: curlymo
  [Solved] Rules switching state based on another device state not working apartmedia 6 3,193 09-27-2017, 01:41 PM
Last Post: apartmedia
  [Solved] connection to main pilight daemon lost TopdRob 20 6,234 09-17-2017, 04:30 PM
Last Post: curlymo
  [Solved] dimmer protocol kaku_dimmer does not react on dimmervalue apartmedia 25 6,247 09-16-2017, 10:29 PM
Last Post: apartmedia
  [Solved] Webgui not working in IE Ulrich.Arnold 7 2,626 09-12-2017, 05:22 PM
Last Post: Ulrich.Arnold
  [Solved] Sunriseset v7 fails after update and gives negative values PPacman 7 2,372 09-06-2017, 06:25 PM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)