DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD Packages and Ports

OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 28th October 2009
marc's Avatar
marc marc is offline
Port Guard
 
Join Date: Jul 2008
Location: Poland
Posts: 25
Thanked 0 Times in 0 Posts
Angry SLiM core dumps

Hello,

Does anyone has any idea why Simple Login Manager [SLiM] is constantly dropping coredumps [slim.core] no matter OBSD version it is running on?
This is quite irritating and I haven't found any answer yet.
I'd like to be able to turn this thing off, but 'ulimit -c 0' doesn't seem to change anything.

Regards
Reply With Quote
  #2   (View Single Post)  
Old 28th October 2009
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 2,901
Thanked 190 Times in 160 Posts
Default

Quote:
Originally Posted by marc View Post
Does anyone has any idea why Simple Login Manager [SLiM] is constantly dropping coredumps [slim.core] no matter OBSD version it is running on?
As this is not an application available in packages/ports, the documentation indicates that it targets Linux:

http://slim.berlios.de/manual.php

Because the filesystem layouts between Linux & OpenBSD are different, you may find code which expects to read/write to a nonexistent location. More information can be found in hier(7) when comparing to information for Linux.

Unless you just happen to run into someone who has ported this application to OpenBSD, I suspect no one will have the specific answer you are hoping to get. In general, porting issues result from:
  • filesystem differences.
  • libraries found in Linux, but not in OpenBSD.
  • differences in the libraries (versions) themselves.
You should also study the compat_linux(8) manpage for additional information.
Reply With Quote
  #3   (View Single Post)  
Old 28th October 2009
marc's Avatar
marc marc is offline
Port Guard
 
Join Date: Jul 2008
Location: Poland
Posts: 25
Thanked 0 Times in 0 Posts
Default

First of all - thank you for your extensive reply.

SLiM is actually available in OpenBSD ports/packages system [slim, slim-themes]. I have linux_compat disabled and I am not using an emulation of any sort.
I have also contacted maintainer of this port, but I haven't got a reply yet.
I can paste bin attachment of slim.core if needed.
Reply With Quote
  #4   (View Single Post)  
Old 28th October 2009
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 3,792
Thanked 214 Times in 189 Posts
Default

A core file will not be of any use to us unless:
  1. We are using the -exact- same OS level and architecture as you.
  2. Your core file was created from an executable containing debugging symbols. That requires manually building the port/package with debugging symbols turned on.
  3. The executable binary file(s), with symbols, is/are made available, also.
Core files are best used on the failing system with gdb(1), to produce backtraces for root cause analysis.

Since the normal package build process strips symbols from executables, it will make your use of an existing core file difficult. I know I've built ports with symbols in the past, but I no longer remember how to do so. I might have set an environment variable or modified the Makefile.

Depending on your debugging and *nix skills, you may consider rebuilding the port with symbols in order to be able to conduct a root cause analysis.

If you don't hear from the port maintainer within the next several days, consider posting a more complete problem report to the ports@ mailing list. You'll need to include a dmesg, SLiM configuration file content, and any other relevant information.

Last edited by jggimi; 28th October 2009 at 04:12 AM.
Reply With Quote
  #5   (View Single Post)  
Old 28th October 2009
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 2,901
Thanked 190 Times in 160 Posts
Default

Quote:
Originally Posted by marc View Post
SLiM is actually available in OpenBSD ports/packages system [slim, slim-themes].
Thanks for the correction. I should have searched with more obvious terms.
Reply With Quote
  #6   (View Single Post)  
Old 28th October 2009
marc's Avatar
marc marc is offline
Port Guard
 
Join Date: Jul 2008
Location: Poland
Posts: 25
Thanked 0 Times in 0 Posts
Default OpenBSD SLiM core dump

Hello again,

So I have a reply from the maintainer [pretty soon] in which he told me to:

cd /usr/ports/x11/slim && DEBUG=-g make reinstall && run slim && get
coredump && gdb /usr/local/bin/slim && core /slim.core && bt full

I went through the aboves [more or less - I am not a coder, but I tried to stick with method, although I had to copy the results manually] and I have some results. I am posting them as the attachments.

Regards
Attached Files
File Type: tgz slim.core.tgz (152.3 KB, 14 views)
File Type: txt slim.txt (4.0 KB, 21 views)
Reply With Quote
  #7   (View Single Post)  
Old 28th October 2009
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 3,792
Thanked 214 Times in 189 Posts
Default

To capture a console session use script(1) in combination with col(1). e.g.:
$ script
Script started, output file is typescript
$ gdb /usr/local/bin/slim /slim.core
GNU gdb 6.3
Copyright...
.
.
.
(gdb) quit
$ exit
Script done, output file is typescript
$ col -b < typescript > my.console.log
Looking through your painstakingly hand-crafted gdb output, here is what I see:
  1. The abort of the application was caused by the attempt to release some memory that was already released. (#2 in the back trace).
  2. X11 services are heavily involved. The last obvious call in use was for _X11TransFreeConnInfo, which is in libX11, after coming from _XDisconnectDisplay.
  3. I do not see any symbols that refer to individual source code lines in your SLiM executable, and I see many lines that say "No symbol table info available." This tells me there is a problem with symbols, but where, I cannot tell from the abbreviated content you were able to capture by hand.
I downloaded your tarball, but it contains only the .core file, and that is useless to me, for all the reasons I stated in my first post: I need to have an exact matching OS release/flavor/architecture, and I must have the executable. But, seeing as how the executable does not appear to have the appropriate/complete symbols within it, I don't know if it would be of any help.
Reply With Quote
  #8   (View Single Post)  
Old 31st October 2009
marc's Avatar
marc marc is offline
Port Guard
 
Join Date: Jul 2008
Location: Poland
Posts: 25
Thanked 0 Times in 0 Posts
Default

I discussed the problem with the maintainer of the port [btw - the maintainer has changed recently] and we seemed to agree, that the whole thing was xfsm-shutdown-helper of xfce4 which didn't allow SLiM to end its session in a clean way, so SLiM generated a coredump. He also forwarded the problem to the new maintainer, so - hopefuly - we'll get a fix soon.
As of my box: I've managed to fix the problem in a very dirty way - little 'hack' performed with the hex editor did the trick for me - at least before the new version comes up.
Reply With Quote
Reply

Tags
core dump, login, manager, openbsd, slim

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
how can I get a core file out of this program TerryP FreeBSD General 4 25th February 2009 07:28 AM
PHP Dumping Core Every 15 seconds?? Michael FreeBSD General 2 21st June 2008 08:17 PM
mc core dump in root sheriff26 FreeBSD General 4 21st June 2008 07:56 PM
bsdtalk: interview with fbsd core ephemera FreeBSD General 1 9th June 2008 12:51 PM
Dual core and FreeBSD ViperChief FreeBSD General 13 2nd June 2008 08:30 PM


All times are GMT. The time now is 03:00 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick