Summary: | kdevelop crashes on start-up | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Tro <tro> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | 3.1.2 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Tro
2004-12-21 05:46:02 UTC
The stderr trace, though verbose, is quite useless to indicate the location of the crash. Please rebuild with debug info and attempt to get a proper backtrace. Reopen if you manage it. I have all kde libraries and kdevelop compiled with debug support. I'm not sure what else I could do. Any suggestions on how to get more information about this crash? Try running kdevelop through gdb. When the crash happens, type 'bt' and you should get the backtrace. Tried that. From what I can tell this will be just as useless, because it's just 1000+ lines of hex addresses. But here it is anyway: http://www.nomorepasting.com/paste.php?pasteID=27493 This is the last bit from kdevelop before I asked for the backtrace: kdevelop: : KDockWidget::setHeader kdevelop: KDockWidgetHeader::showUndockButton(true) kmdi: *****void KMDIGUIClient::addToolView(KMdiToolViewAccessor* mtva)***** kmdi: KMDIGUIClient::setupActions: plugActionList kmdi: *** KDockWidgetHeader has been found kmdi: NAMENAMENAMENAME:===========================:Valgrind kmdi: KMdiDockContainer::insertWidget() kmdi: ***********************************Setting tooltip for a widget: Valgrind memory leak check Program received signal SIGSEGV, Segmentation fault. 0xb6dddb5e in ?? () If it helps any, when SIGSEGV was sent, KDevelop was "Loading: Tools Menu Addition". Wow, that's the emptiest backtrace I've ever seen. :) The bt is of course useless. There is still nothing here for us to use. Are you sure you have debug info compiled in? What's the size of the /usr/bin/kdevelop binary? No wild optimization flags? 1.2M kdevelop CFLAGS="-O2 -march=pentium4 -pipe -fomit-frame-pointer -fstack-protector" I needed -fstack-protector to compile aRts earlier. But I just removed it and recompiled. It didn't make a difference. I managed to sqeeze out a (hopefully) useful line from the backtrace by downgrading to gcc 3.3.5 and recompiling kdevelop. http://www.nomorepasting.com/paste.php?pasteID=29853 I'm not sure if this will make any difference, so I'm not reopening the bug. It's just FYI. I am now in the process of recompiling my entire system with gcc 3.3.5 to see if it helps me get more info. Hopefully, I'll have something useful to report next time. :) Your optimization flags don't look too crazy to me, but you probably won't get a good backtrace until you remove them and use -g3 instead. Just did that. No gain. :( I am noticing this happening too. I installed form the gentoo portage the other day and had no troubles using kdevelop. My flags aren't to crazy either, just the normal stuff for a p4 (CFLAGS="-O3 -march=pentium4 -fomit-frame-pointer -pipe -msse2"). I also am using gcc 3.3.5. |