Closed GoogleCodeExporter closed 9 years ago
Did you compile from source or install via the .debs? The .deb files are only
for specific versions of Ubuntu.
If you did install via one of the .deb files, then it appears that the version
of Qt you have on your system is not binary compatible with the version that
comes with the Ubuntu system it was compiled on.
I would definitely recommend you try compiling from the sources and let me know
if it is still an issue.
Thanks!
Original comment by evan.teran
on 3 Oct 2012 at 5:17
I've the same issue with the 0.9.18 Release from the source on a Debian i686
System. The SVN Version starts but crashes when I attempt to attach or start a
program.
Original comment by evan.teran
on 3 Oct 2012 at 5:17
Attachments:
Is this still an issue? And just to be clear, this happens when building from
**source**?
The reason I ask is that the missing symbol after demangling is
"QListData::detach_grow(int*, int)" which is clearly part of Qt itself. Not
only that, but it's an internal part of Qt (not used directly by any edb source
code).
When this type of thing happens, it is usually because the binary was built
against a different version of the Qt library than the one trying to be used to
run it. Are you sure your development headers version's match that of the Qt
libraries installed on your system?
Please let me know.
Evan Teran
Original comment by evan.teran
on 3 Oct 2012 at 5:18
Sorry for the late update.
EDB seems to mix paths. I had an old build in ~/Downloads/Debugger/debugger/
and a fresh svn and stable copy in ~/Programming/EDB/. When I started edb in
stable I got this look-up error (in my case it was in libFunctionDB) and then
realized it where a different path! So the error occured in
~/Downloads/Debugger/debugger/. I don't know why it searched there I hadn't had
any $PATH etc. set, so I would guess its in a user-wide config of edb. However
I deleted the folder and now both versions are working. Noticable is that they
still try to retrieve symbols from ~/Downloads.
I'm not sure how far this is relevant for OP, but for me it is "solved as in
its working".
gxntr
Original comment by evan.teran
on 3 Oct 2012 at 5:18
Original comment by evan.teran
on 3 Oct 2012 at 5:18
I have not been able to replicate this issue in any recent version of edb. I
believe it has been addressed.
Original comment by evan.teran
on 9 Aug 2013 at 2:59
Original issue reported on code.google.com by
evan.teran
on 3 Oct 2012 at 3:22