Freeze after openning a file.

[GoogleCodeExporter]

Created attachment 21
gdb's_output

Hi,
after attempting to open (or attach to a running) program (a "Hello World!" or 
whatever), EDB completely freeze.
The Cpu Usage of EDB is reaching 100%.

The program being debbuged stops running, and htop display its state as 
"traced/stopped".

The output of EDB is:

Starting edb version: 0.9.18 
Please Report Bugs & Requests At: http://bugs.codef00.com/
[load_plugins] Loading Plugin: libAnalyzer.so                 : 0x236ca10
[load_plugins] Loading Plugin: libBinarySearcher.so           : 0x2397210
[load_plugins] Loading Plugin: libBookmarks.so                : 0x239c900
[load_plugins] Loading Plugin: libBreakpointManager.so        : 0x23ae3a0
[load_plugins] Loading Plugin: libCheckVersion.so             : 0x237cc50
[load_plugins] Loading Core Plugin: libDebuggerCore.so        : 0x23a38e0
[load_plugins] Loading Plugin: libDumpState.so                : 0x23e1b40
[load_plugins] Loading Plugin: libELFBinaryInfo.so            : 0x23d5970
[load_plugins] Loading Plugin: libEnvironment.so              : 0x23e32f0
[load_plugins] Loading Plugin: libFunctionFinder.so           : 0x23e36d0
[load_plugins] Loading Plugin: libHardwareBreakpoints.so      : 0x23e4a80
[load_plugins] Loading Plugin: libHeapAnalyzer.so             : 0x23e3eb0
[load_plugins] Loading Plugin: libOpcodeSearcher.so           : 0x23e4e90
[load_plugins] Loading Plugin: libOpenFiles.so                : 0x23e3ee0
[load_plugins] Loading Plugin: libReferences.so               : 0x23e72a0
[load_plugins] Loading Plugin: libROPTool.so                  : 0x23e8c00
[load_plugins] Loading Plugin: libSessionManager.so           : 0x23e8bb0
[load_plugins] Loading Plugin: libStringSearcher.so           : 0x23e8f80
[load_plugins] Loading Plugin: libSymbolViewer.so             : 0x23e9c20
[load_plugins] Loading Plugin: libAnalyzer.so                 : 0x2392730
[load_plugins] Loading Plugin: libBinarySearcher.so           : 0x2391a00
[load_plugins] Loading Plugin: libBookmarks.so                : 0x23a25c0
[load_plugins] Loading Plugin: libBreakpointManager.so        : 0x239cc80
[load_plugins] Loading Plugin: libCheckVersion.so             : 0x239e320
[load_plugins] Loading Plugin: libDumpState.so                : 0x23ef9f0
[load_plugins] Loading Plugin: libELFBinaryInfo.so            : 0x23f2530
[load_plugins] Loading Plugin: libEnvironment.so              : 0x23f46c0
[load_plugins] Loading Plugin: libFunctionFinder.so           : 0x23f3100
[load_plugins] Loading Plugin: libHardwareBreakpoints.so      : 0x23f5180
[load_plugins] Loading Plugin: libHeapAnalyzer.so             : 0x23f6b70
[load_plugins] Loading Plugin: libOpcodeSearcher.so           : 0x23f2880
[load_plugins] Loading Plugin: libOpenFiles.so                : 0x23f8ce0
[load_plugins] Loading Plugin: libReferences.so               : 0x23f9a30
[load_plugins] Loading Plugin: libROPTool.so                  : 0x23f9970
[load_plugins] Loading Plugin: libSessionManager.so           : 0x23fb1b0
[load_plugins] Loading Plugin: libStringSearcher.so           : 0x23fba80
[load_plugins] Loading Plugin: libSymbolViewer.so             : 0x23fc7a0
comparing versions: [2322] [2322]
comparing versions: [2322] [2322].

The output of gdb (debugging a debugger, how cool is that ?) is in the 
attachement.

I am on Archlinux x86_64, kernel version 3.4.9-1, thanks.

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

[GoogleCodeExporter]

Interesting,

Well the first thing I'm noticing is that it looks like your are loading 2 sets 
of plugins. This can often cause unusual problems, so let's address that first.

This typically happens because EDB has 2 search directories.

It will first search in the directory specified in the settings.
Then it will also load any plugins in the current working directory (so users 
can load custom plugins if desired while still using the ones in the system 
install path).

anyway, to check the system location open preferences:

Options -> Configure Debugger

Then goto the "Directories" tab.

Then look at the "Plugin Directory" entry.

Now that we know where the plugins are coming from, please do what you need to 
do to prevent one or the other from being loaded.

If after that the problem persists, let me know.

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

• Changed state: Accepted

[GoogleCodeExporter]

(In reply to comment #1)
> Interesting,
> 
> Well the first thing I'm noticing is that it looks like your are loading 2 
sets
> of plugins. This can often cause unusual problems, so let's address that 
first.
> 
> This typically happens because EDB has 2 search directories.
> 
> It will first search in the directory specified in the settings.
> Then it will also load any plugins in the current working directory (so users
> can load custom plugins if desired while still using the ones in the system
> install path).
> 
> anyway, to check the system location open preferences:
> 
> Options -> Configure Debugger
> 
> Then goto the "Directories" tab.
> 
> Then look at the "Plugin Directory" entry.
> 
> Now that we know where the plugins are coming from, please do what you need to
> do to prevent one or the other from being loaded.
> 
> If after that the problem persists, let me know.

Hi,
thank you very much for your answer.

The problem was that I compiled EDB with
$ qmake -makefile DEFAULT_PLUGIN_PATH="/usr/lib/edb/"
$ make

And installed it with
$ make install (And not "make INSTALL_ROOT=/usr/ install" as I should have)

, which is kind of stupid..

Anyways, changing the plugin directory to the "installation path

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

[GoogleCodeExporter]

Hi,
thank you very much for your answer.

The problem was that I compiled EDB with
$ qmake -makefile DEFAULT_PLUGIN_PATH="/usr/lib/edb/"
$ make

And installed it with
$ make install (And not "make INSTALL_ROOT=/usr/ install" as I should have)

, which is kind of stupid..

Anyways, changing the plugin directory to the "installation path" solved the 
problem.

Thanks for this, and the awesome work you've done in creating a real debugger 
for Linux.

Live long and prosper.

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

Attachments:

• gdb's_output

[GoogleCodeExporter]

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

• Changed state: Fixed