wuhailinjerry / edb-debugger

Automatically exported from code.google.com/p/edb-debugger
GNU General Public License v2.0
0 stars 0 forks source link

libAnalyzer.so: symbol lookup error. #118

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Hi,
the usage of the "Analyser" or the "FunctionFinder" plugins provoke the crash 
of EDB.

Output:
Starting edb version: 0.9.18 
Please Report Bugs & Requests At: http://bugs.codef00.com/
[load_plugins] Loading Plugin: libAnalyzer.so                 : 0x1c518d0
[load_plugins] Loading Plugin: libBinarySearcher.so           : 0x1dbf8d0
[load_plugins] Loading Plugin: libBookmarks.so                : 0x1dd5e40
[load_plugins] Loading Plugin: libBreakpointManager.so        : 0x1dd79d0
[load_plugins] Loading Plugin: libCheckVersion.so             : 0x1c31c50
[load_plugins] Loading Core Plugin: libDebuggerCore.so        : 0x1c549d0
[load_plugins] Loading Plugin: libDumpState.so                : 0x1da96b0
[load_plugins] Loading Plugin: libELFBinaryInfo.so            : 0x1d97680
[load_plugins] Loading Plugin: libEnvironment.so              : 0x1d6ad00
[load_plugins] Loading Plugin: libFunctionFinder.so           : 0x1da0430
[load_plugins] Loading Plugin: libHardwareBreakpoints.so      : 0x1c46790
[load_plugins] Loading Plugin: libHeapAnalyzer.so             : 0x1d9d680
[load_plugins] Loading Plugin: libOpcodeSearcher.so           : 0x1da0350
[load_plugins] Loading Plugin: libOpenFiles.so                : 0x1da8530
[load_plugins] Loading Plugin: libReferences.so               : 0x1db0c30
[load_plugins] Loading Plugin: libROPTool.so                  : 0x1c61870
[load_plugins] Loading Plugin: libSessionManager.so           : 0x1da8760
[load_plugins] Loading Plugin: libStringSearcher.so           : 0x1d90660
[load_plugins] Loading Plugin: libSymbolViewer.so             : 0x1d8e840
comparing versions: [2322] [2322]
loading symbols: "/home/mscofield/EDB/debugger/x.map" 
loading symbols: "/home/mscofield/EDB/debugger/ld-2.16.so.map" 
loading symbols: "/home/mscofield/EDB/debugger/[vdso].map" 
loading symbols: "/home/mscofield/EDB/debugger/[vsyscall].map" 
[SessionManager] loading session file: "/home/mscofield/EDB/debugger/x.edb" 
for: "/home/mscofield/C/x" 
[Analyzer] identifying executable headers...
[Analyzer] adding entry points to the list...
[Analyzer] found entry point: 0x400410
[Analyzer] attempting to add 'main' to the list...
No main symbol found, calculated it to be 00000000004004fc using heuristic
[Analyzer] attempting to add marked functions to the list...
[Analyzer] attempting to add functions with symbols to the list...
[Analyzer] adding: x::_init <0x4003a8>
[Analyzer] adding: x::printf@plt <0x4003e0>
[Analyzer] adding: x::__libc_start_main@plt <0x4003f0>
[Analyzer] adding: x::__gmon_start__@plt <0x400400>
[Analyzer] adding: x::_start <0x400410>
[Analyzer] adding: x::deregister_tm_clones <0x400440>
[Analyzer] adding: x::register_tm_clones <0x400470>
[Analyzer] adding: x::__do_global_dtors_aux <0x4004b0>
[Analyzer] adding: x::frame_dummy <0x4004d0>
[Analyzer] adding: x::main <0x4004fc>
[Analyzer] adding: x::__libc_csu_init <0x400520>
[Analyzer] adding: x::__libc_csu_fini <0x4005b0>
[Analyzer] adding: x::_fini <0x4005b4>
[Analyzer] calculating function bounds... (pass 1)
edb: symbol lookup error: /home/mscofield/EDB/debugger/libAnalyzer.so: 
undefined symbol: _ZN11InstructionIN8edisassm6x86_64EEC1EPKhmmRKSt9nothrow_t

This happens with different unrelated binaries.

Thanks.

Original issue reported on code.google.com by evan.teran on 3 Oct 2012 at 3:22

GoogleCodeExporter commented 9 years ago
Firstly,
Sorry you're having difficulty with edb. I'm sure we'll figure it out.

Next,
I see that you have the plugins loading correctly, does this mean that I can 
close bug #117?

OK, now on to the bug. So for some reason, the linker is not finding:

Instruction<edisassm::x86_64>::Instruction(unsigned char const*, unsigned long, 
unsigned long, std::nothrow_t const&)

My main question is this. Are you installing via a package? from source? If 
from source, SVN or numbered release?

The reason I ask is that I made some changes to edisassm a while ago and while 
I don't *think* it should have made a difference, it's of course possible.

If you compiled from source, please give the SVN version a try as it is far 
more up to date.

Let me know,
Thanks for you patients,
Evan

Original comment by evan.teran on 3 Oct 2012 at 5:33

GoogleCodeExporter commented 9 years ago
Hi, thanks for your answer.

I was using the sources from the home page 
(codef00.com/projects/debugger-0.9.18.tgz), and I can't compile the sources 
from the SVN cause of this bug #119.

Thanks ;)

Original comment by evan.teran on 3 Oct 2012 at 5:33

GoogleCodeExporter commented 9 years ago
Having the same issue with self-compiled 0.9.18. After compiling from SVN 
(0.9.19) everything went fine and issue resolved.

Original comment by archer07...@gmail.com on 24 Mar 2013 at 2:00

GoogleCodeExporter commented 9 years ago
Seems to be resolved int he latest SVN.

Original comment by evan.teran on 26 Jul 2013 at 1:54