FS#35644 - [gkrellm] dumps core
Attached to Project:
Community Packages
Opened by Geoff (perseus) - Tuesday, 04 June 2013, 16:42 GMT
Last edited by Balló György (City-busz) - Wednesday, 25 December 2013, 09:39 GMT
Opened by Geoff (perseus) - Tuesday, 04 June 2013, 16:42 GMT
Last edited by Balló György (City-busz) - Wednesday, 25 December 2013, 09:39 GMT
|
Details
Description:
I am guessing that bug this is probably upstream or specific to my machine and/or configuration, but I will report it here in case I am wrong. The gkrellm mailing list seems to be down and the developer has not yet responded to an e-mail sent a few days ago. gkrellm has been reliable on this machine (using icewm as my WM), for about 5 years. In the past month or so it has begun to crash and dump core. There have been no changes to my system in that time except for the daily 'pacman -Syu' Sometimes this happens after hours of starting gkrellm, sometimes after days. Generally it is after 3 or 4 hours. When runniing from an xterm, the last line is: aborted: Sensors (update_monitor) Aborted (core dumped) I am inexpert, but I have tried running under gdb. It never crashes when I do this. I have also run using the script command with a 2>&1 session. The output after the most recent crash is at the top of the attached gkrellm.txt. The crash also leaves a lot of output in the xterm, much of which has probably scrolled off. What I can still see is the second part of gkrellm.txt. I don't want to make this report overlong. If someone tells me what else may be needed, I will (of course), respond. Additional info: * package version(s) 2.3.5-4 * config and/or log files etc - attached gkrellm.txt Steps to reproduce: Simply run the program and wait. |
This task depends upon
Closed by Balló György (City-busz)
Wednesday, 25 December 2013, 09:39 GMT
Reason for closing: Upstream
Wednesday, 25 December 2013, 09:39 GMT
Reason for closing: Upstream
I have put my user_config & sensor_config in the attached configs.txt
The last crash occured after 12 hours of gkrellm uptime (this box is on 24/7). As usual it occurred randomly (so far as I an tell), when I had been away from the machine for hours.
I have gone back to running under gdb - starting 12 hours ago. So far there has been no crash - but I have never had a crash while running under gdb. I don't know what to look for in the non-crash output of gdb - what I see is an endless sequence of "New Thread" .. eg :
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0xb2e74b40 (LWP 11249)]
[Thread 0xb2e74b40 (LWP 11249) exited]
[New Thread 0xb2e74b40 (LWP 11252)]
[Thread 0xb2e74b40 (LWP 11252) exited]
... etc (the current total is > 19,000 of these/
It occurs to me that the problem may have started when lm_sensors was updated on 12th May (there has been subsequent update, as you will know). I only keep the last two versions of packages, but I could try finding / installing the previous one if that might help.
According to the README file, an alternative is to build it via "make without-libsensors=yes".
If you decide to shift this package back to the AUR, please notify me after doing so and I'll adopt it.
I have a similar situation. Gkrellm was working fine and recently it started dumping core for me. Sometimes within a few minutes of starting it.
Oct 15 17:18:10 t61p systemd-coredump[1979]: Process 1858 (gkrellm) dumped core.
-- Subject: Process 1858 (gkrellm) dumped core
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
--
-- Process 1858 (gkrellm) crashed and dumped core.
--
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
I would prefer you guys don't drop it. I can write some code, if possible I'll help. I guess the first thing I could do is find the core file and see if I can back trace it. Any idea where I could find it? find / -name core?
Please let me know if I can help fix this.
No problems here with ati/mesa drivers