Summary: | C++ completion crashes kdevelop | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Grzegorz Jaskiewicz <gj> |
Component: | general | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | bzipped valgrind log, (caution : 111MB after unpacking!) |
Description
Grzegorz Jaskiewicz
2004-02-27 00:39:58 UTC
dupe again. *** This bug has been marked as a duplicate of 74664 *** Created attachment 4910 [details]
bzipped valgrind log, (caution : 111MB after unpacking!)
just runned it with valgrind though, my dbd version is 4.2
gj@ysl-dev:~$ ldd /opt/kde/lib/libkdevcatalog.so
libdb-4.2.so => /usr/lib/libdb-4.2.so (0x40024000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x400fa000)
libm.so.6 => /lib/libm.so.6 (0x401b4000)
libc.so.6 => /lib/libc.so.6 (0x401d6000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40309000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x8000000
I guess configure script should pickup right one, cos this one is obvioulsy not
the one application was developed for.
sorry folks about long attachment, bzip2 -d file.bz2|grep -v pthread>kdevelop-valgrind.log should help ;) |