|
OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
Quote:
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:
|
|
||||
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. |
|
||||
A core file will not be of any use to us unless:
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. |
|
|||
Thanks for the correction. I should have searched with more obvious terms.
|
|
||||
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 |
|
||||
To capture a console session use script(1) in combination with col(1). e.g.:
$ scriptLooking through your painstakingly hand-crafted gdb output, here is what I see:
|
|
||||
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. |
Tags |
core dump, login, manager, openbsd, slim |
Thread Tools | |
Display Modes | |
|
|
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 |