Project

General

Profile

Bug #5886

Crash

Added by Gerog De 7 months ago. Updated 6 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
General
Target version:
-
Start date:
2020-05-01
Due date:
% Done:

0%

Estimated time:
Found in version:
4.3.1-1857
Affected Versions:

Description

May 1 01:13:57 streamer01 tvheadend4125: CRASH: Fault address 0xffff4550 (Address not mapped)
May 1 01:13:57 streamer01 tvheadend4125: CRASH: Loaded libraries: linux-vdso.so.1 /usr/lib/x86_64-linux-gnu/libdvbcsa.so.1 /usr/lib/x86_64-linux-gnu/libssl.so.1.1 /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 /lib/x86_64-linux-gnu/libz.so.1 /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0 /usr/lib/x86_64-linux-gnu/liburiparser.so.1 /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 /lib/x86_64-linux-gnu/libdbus-1.so.3 /lib/x86_64-linux-gnu/libdl.so.2 /lib/x86_64-linux-gnu/libpthread.so.0 /lib/x86_64-linux-gnu/libm.so.6 /lib/x86_64-linux-gnu/librt.so.1 /lib/x86_64-linux-gnu/libmvec.so.1 /usr/lib/x86_64-linux-gnu/libstdc++.so.6 /lib/x86_64-linux-gnu/libc.so.6 /lib/x86_64-linux-gnu/libsystemd.so.0 /lib64/ld-linux-x86-64.so.2 /lib/x86_64-linux-gnu/libgcc_s.so.1 /lib/x86_64-linux-gnu/liblzma.so.5 /usr/lib/x86_64-linux-gnu/liblz4.so.1 /lib/x86_64-linux-gnu/libgcrypt.so.20 /lib/x86_64-linux-gnu/libgpg-error.so.0 /lib/x86_64-linux-gnu/libnss_compat.so.2 /lib/x86_64-linux-gnu/libnss_nis.so.2 /lib/x86_64-linux-gnu/libnsl.so.1
May 1 01:13:57 streamer01 tvheadend4125: CRASH: Register dump [23]: 00007f73d0054570000000000000000000007f73d00008d0000000000000000000007f736c014e0800000000ffff45500000000000000080000000000000000a00000000ffff4550000000000000000000007f73d00545a800007f73d005457000007f73d005460000000000ffff4550000000000000055000007f73fcbea7a800007f74000826460000000000010297002b0000000000330000000000000004000000000000000efffffffe7ffbba1300000000ffff4550
May 1 01:13:57 streamer01 tvheadend4125: CRASH: STACKTRACE
May 1 01:13:58 streamer01 tvheadend4125: CRASH: /home/djole/tvheadend/tvheadend/tvheadend/src/trap.c:176 0x556b71d8b9fd 0x556b71b76000
May 1 01:13:58 streamer01 tvheadend4125: CRASH: ??:0 0x7f7400f2d890 0x7f7400f1b000
May 1 01:13:58 streamer01 tvheadend4125: CRASH: ??:0 0x7f7400082646 0x7f73fffd1000
May 1 01:13:59 streamer01 tvheadend4125: CRASH: /home/djole/tvheadend/tvheadend/tvheadend/src/tvh_string.h:84 (discriminator 4) 0x556b71d75604 0x556b71b76000
May 1 01:13:59 streamer01 tvheadend4125: CRASH: /home/djole/tvheadend/tvheadend/tvheadend/src/input/mpegts/mpegts_service.c:361 0x556b71e1c830 0x556b71b76000
May 1 01:13:59 streamer01 tvheadend4125: CRASH: /home/djole/tvheadend/tvheadend/tvheadend/src/service.c:412 0x556b71d75bd7 0x556b71b76000
May 1 01:14:00 streamer01 tvheadend4125: CRASH: /home/djole/tvheadend/tvheadend/tvheadend/src/subscriptions.c:336 (discriminator 4) 0x556b71d70219 0x556b71b76000
May 1 01:14:00 streamer01 tvheadend4125: CRASH: /home/djole/tvheadend/tvheadend/tvheadend/src/subscriptions.c:409 0x556b71d71cb0 0x556b71b76000
May 1 01:14:00 streamer01 tvheadend4125: CRASH: /home/djole/tvheadend/tvheadend/tvheadend/src/main.c:706 0x556b71d3dde9 0x556b71b76000
May 1 01:14:00 streamer01 tvheadend4125: CRASH: /home/djole/tvheadend/tvheadend/tvheadend/src/tvh_thread.c:91 0x556b71d4b7f8 0x556b71b76000
May 1 01:14:01 streamer01 tvheadend4125: CRASH: ??:0 0x7f7400f226db 0x7f7400f1b000
May 1 01:14:01 streamer01 tvheadend4125: CRASH: clone+0x3f (/lib/x86_64-linux-gnu/libc.so.6)
May 1 01:14:01 streamer01 kernel: [ 395.576892] tvh:mtimer4131: segfault at ffff4550 ip 00007f7400082646 sp 00007f73fcbea7a8 error 4 in libc-2.27.so[7f73fffd1000+1e7000]
May 1 01:14:01 streamer01 kernel: [ 395.576914] Code: 0f 1f 40 00 66 0f ef c0 66 0f ef c9 66 0f ef d2 66 0f ef db 48 89 f8 48 89 f9 48 81 e1 ff 0f 00 00 48 81 f9 cf 0f 00 00 77 6a <f3> 0f 6f 20 66 0f 74 e0 66 0f d7 d4 85 d2 74 04 0f bc c2 c3 48 83
May 1 01:14:01 streamer01 systemd1: tvheadend.service: Main process exited, code=killed, status=11/SEGV
May 1 01:14:01 streamer01 systemd1: tvheadend.service: Failed with result 'signal'.


Files

History

#1

Updated by Victor S 7 months ago

They wont take your report, crash is not useable. They ask to install debug package, which is being unknown how to install, I can't find any info where to get it.

#2

Updated by Flole Systems 7 months ago

Victor S wrote:

They wont take your report, crash is not useable. They ask to install debug package, which is being unknown how to install, I can't find any info where to get it.

This is a valid and usable crash report (see the wiki for reference), the debug package has been installed. It's located at exactly the same location where the tvheadend package is aswell, not hard to find at all (assuming that someone actually wants to find it). Its even described in the Wiki, so you are just not reading properly. Nobody will spoon feed information to someone here, even though you are behaving like a baby that needs spoon feeding you are treated like an adult here. That means you need to get information yourself and do research yourself, which you seem to be not capable of unfortunately.

Stop spamming in here, this is my last warning! When you don't have anything to say that helps solving an issue just don't comment. Tvheadend is not the right software for you as you need a software that offers a support contract with a service level agreement and a guranteed time for solving issues. Tvheadend doesn't offer this, issues are fixed when someone wants to fix them, support is provided on a "help yourself" basis and there is nothing you can do about that. You are complaining the entire time instead of fixing your own issue. The reason your problem is not fixed is that you are not working on it actively and are spamming in here and keeping people busy re-verifying old bugs and telling you that they are fixed.

TLDR: Gerog De did nothing wrong, the report is perfectly fine (other than being a duplicate maybe). Victor S is just not happy with the amount of free of charge support he is receiving and is expressing this by his toxic and immature behaviour.

#3

Updated by Victor S 7 months ago

Flole Systems wrote:

Victor S wrote:

They wont take your report, crash is not useable. They ask to install debug package, which is being unknown how to install, I can't find any info where to get it.

This is a valid and usable crash report (see the wiki for reference), the debug package has been installed. It's located at exactly the same location where the tvheadend package is aswell, not hard to find at all (assuming that someone actually wants to find it). Its even described in the Wiki, so you are just not reading properly. Nobody will spoon feed information to someone here, even though you are behaving like a baby that needs spoon feeding you are treated like an adult here. That means you need to get information yourself and do research yourself, which you seem to be not capable of unfortunately.

Stop spamming in here, this is my last warning! When you don't have anything to say that helps solving an issue just don't comment. Tvheadend is not the right software for you as you need a software that offers a support contract with a service level agreement and a guranteed time for solving issues. Tvheadend doesn't offer this, issues are fixed when someone wants to fix them, support is provided on a "help yourself" basis and there is nothing you can do about that. You are complaining the entire time instead of fixing your own issue. The reason your problem is not fixed is that you are not working on it actively and are spamming in here and keeping people busy re-verifying old bugs and telling you that they are fixed.

TLDR: Gerog De did nothing wrong, the report is perfectly fine (other than being a duplicate maybe). Victor S is just not happy with the amount of free of charge support he is receiving and is expressing this by his toxic and immature behaviour.

Instead of lecturing me, you could spend a second and post exact link where it says about debug package and how to install it. And no, there is no debug package in the folder, and not in apt. I had to spend a whole day reading a Make file and forcing it to compile debug, because of such a "guess yourself" wiki. What kind of feedback you expect after this?
Or what you gonna do? Ban my account?

"Incorrect (not useable) crash reports" refers to anything "Address not mapped", that is what topic started has. Perhaps you need to make it more readable page for users, not 10 years experienced devs. https://tvheadend.org/projects/tvheadend/wiki/Debugging

#4

Updated by Flole Systems 7 months ago

You even posted the link yourself.... As mentioned above, I do not do spoon feeding. Assuming that you are using Debian/Ubuntu (why else would you use apt otherwise) there is a dbg package after using the Autobuild script and in the apt repo there is one aswell. This all of course assumes that you read and followed the instructions. If you wasted your time spent your time wisely by learning more about how a Makefile works that's a solution aswell (although it's definitely not the normal or recommended way).

In the Bug Tracker I don't expect any feedback, just bugs and feature requests.

Is "Address not mapped" the only difference you see in the wiki? That small detail is the only difference you noticed when looking at those stacktraces that look completely different? Anyways, when you don't know what you are doing, don't try to "help" others. And helping also includes (in this case) your toxic behavior of spamming and complaining everywhere like a baby. Any dev who has ever read a stacktrace will notice that the first stacktrace in the wiki is not readable when they try to read it. If you are not a dev, don't try to read the stack trace. You won't understand it anyways. Learn how to read a stacktrace first, then go to the wiki (or to one of your bug reports) and try to read the stacktrace and tell me where the program was when it crashed. You will notice that it is not possible, that's why it's unusable.

#5

Updated by Victor S 7 months ago

Very well, see the screenshot, where is it?? This is your repo and Autobuild is what I launched. Am I blind or what?

#6

Updated by Victor S 7 months ago

Oh no, even better, a "crying baby" know find command. Amazing.

:~/tvheadend# find . -name *.deb
:~/tvheadend#

#7

Updated by Flole Systems 7 months ago

That means you did something wrong. Check the buildlog of doozer (https://doozer.io/tvheadend/tvheadend/buildlog/20497) which also uses Autobuild and look what packages it is building (mentioned in the log aswell). If that is not what you are getting either the requirements are not met. There are Build Instructions and Packaging instructions in the wiki (which you most likely ignored aswell).

#8

Updated by Victor S 7 months ago

Nope, everything is right. Assuming it would build the packages automatically, and if something wasn't met, it would abort the compilation, but it didn't. Anyway, I wrote a solution in my ticket for those who fill find it useful in such cases.

Also available in: Atom PDF