Segfault error 4 in libc.so.6 #124
Comments
|
Can you try to use this with the lowest supported version of Theengs Decoder? |
|
Wait, we didn't have a TheengsDecoder package then, ignore that suggestion 🙂 |
|
Already installed TheengsDecoder version 1.3.0 and under testing 🙂 |
|
No I'm curious now that it's under testing whether something in a recent Decoder release leads to your issue. |
|
Error occurs again with version 1.3.0:
|
|
Ok, I think you'll need to investigate the core dump. Are you able to do that? You need to install the |
|
Unfortunately I'm not a programmer :/. Maybe somebody else can help ? |
|
Do you see whether this segfault always occurs after decoding a specific Bluetooth device? Or is it random? What's the latest decoding you see as an MQTT message or in the Gateway's console output before it segfaults? |
|
By the way, can you try running with log_level set to INFO instead of DEBUG to see whether that makes a difference? |
|
In logs I see that segfault appears after these two: `DEBUG:BLEGateway:D2:64:5C:XX:XX:XX:AdvertisementData(local_name='RDL52832', manufacturer_data= DEBUG:BLEGateway:D9:1C:BC:XX:XX:XX:AdvertisementData(local_name='RDL52832', manufacturer_dat It seems it happens when beacon appears in a system, but randomly and it must be gone for longer time, because when I hide it for a while and shows again, it works properly. I'll try with INFO level. |
|
Can you try to disable the RDL52832 devices, e.g. by removing their battery? If the gateway doesn't crash after this, then the segfault is probably triggered by the RDL52832 decoder. |
|
This time it was working quite longer without RDL in a system, but even RDL it's a cause, I think it would be better to ask somebody for analyze to prevent such cases. This beacon is a great solution for presence detection. |
m_docMax Test to see possible changed behaviour for theengs/gateway#124
m_docMax Test to see possible changed behaviour for theengs/gateway#124
|
Could you try with the new Theengs Gateway release v1.0.0, to see if it changes anything for you? Thanks |
|
@DigiH issue still exists 😢 , coredump attached if needed. |
|
Should I provide anything else to help ? Edit: |
|
I just read that the RDL52832 might be causing your issue, so I implemented the above change on the Decoder side. Unfortunately I don't have enough knowledge on the Gateway Python side to test and see what your issue might still be :( |
|
Details from dump if it can helps:
|
|
Many crashes I've also noticed just after: |
In case this undecoded and unknown "LE_WH-1000XM4" headset, with its very long servicedata and manufacturerdata, is actually the cause of the crash, could you test starting with -pa 0
|
I've noticed recently,, that I'm getting segfault quite often
Apr 6 11:07:17 openhab kernel: [ 2958.011031] python3[13034]: segfault at 0 ip 00007f332d7753bd sp 00007f332adb8df8 error 4 in libc.so.6 [7f332d622000+179000] Apr 6 11:07:17 openhab kernel: [ 2958.011077] Code: e1 c5 f8 77 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 <c5> fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66Coredump in attachment.
core.python3.0.d17642bc1c99473cad951ae65472ba6b.9616.1680771946000000.zst.zip
Environment
Output of
python -m TheengsGateway.diagnoseTheengs Gateway Diagnostics
Package Versions
Python
Operating System
Configuration
Bluetooth adapters
Default adapter: hci0
hci0
The text was updated successfully, but these errors were encountered: