| Summary: | Amarok Won't start w/ 4k stacks enabled in kernel | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Aaron Rusnak <aaronrusnak> |
| Component: | general | Assignee: | Amarok Bugs <amarok-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 1.0.1 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Aaron Rusnak
2004-07-03 18:06:58 UTC
i'm having the exact same problem, running 2.6.7 vanilla with 4k stacks enabled! Backtrace please :) gdb amarokapp run [wait for crash] bt [hb@pulse]$ gdb amarok ~ GNU gdb 6.0 Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/kde/3.2/bin/amarok warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. [amaroK loader] connecting to /home/hb/.kde//socket-pulse/amarok.loader_socket [amaroK loader] amaroK not running. Trying to start it.. Detaching after fork from child process 14227. Detaching after fork from child process 14228. [amaroK loader] timed out trying to contact to amaroK. [amaroK loader] exiting. Program exited normally. (gdb) bt No stack. (gdb) oh, i mixed up amarok with amarokapp so here for amarokapp: [hb@pulse]$ gdb amarokapp ~ GNU gdb 6.0 Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/kde/3.2/bin/amarokapp warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. Program received signal SIGSEGV, Segmentation fault. 0x00000000 in ?? () (gdb) bt #0 0x00000000 in ?? () (gdb) I'm afraid this backtrace is useless.. maybe we can get a valid one from another user. (gdb) run Starting program: /usr/kde/3.2/bin/amarokapp warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. warning: shared library handler failed to enable breakpoint Program received signal SIGSEGV, Segmentation fault. 0x00000000 in ?? () (gdb) bt #0 0x00000000 in ?? () #1 0x415d6545 in ?? () #2 0x420f5a70 in ?? () #3 0x0814d2d0 in ?? () #4 0x4171d49e in ?? () #5 0x41748698 in ?? () ...... #790 0x00000000 in ?? () Cannot access memory at address 0xc0000000 The list goes up to #790 of memory addresses (i think). My backtrace is pretty useless too. Can I compile with --enable-debug for a better backtrace? Well... I figured out it wasn't 4K stacks causing this problem. I remembered I upgraded my Nvidia Drivers to the latest 1.0.6106 drivers, and somehow amarok won't even start with them. I've downgraded to 1.0.5336, and amarok starts up fine and works perfect now. I've also switched back to 8K stacks in the kernel, and amarok still would not load using the new nvidia drivers. Something must've got broken for video playback with the new set of drivers. I guess file as resolved unless someone else can verify that amarok won't load with 4K stacks enabled and not using any nvidia drivers. Thanks for clarification. Closing now. If problems with NVidia driver persist and can be traced to amaroK, please open a separate report. |