Emulator hang when track_by_pid

[GoogleCodeExporter]

Steps to produce the problem:
1. Run the emulator, load the plugin.
2. Start 'Calculator' app
3. Use trace_by_pid to trace the app
4. On the emulator screen, push at about 20 ~ 50 buttons of the calculator.
5. Initially, the instructions are correctly printed, but later the emulator 
and the Qemu monitor become unresponsive.

Is it a known issue?

I patched the code using the file DroidScope_Alpha_2.diff in the Downloads page 
and the links provided in the Wiki page.
The Android source code I use is 2.3.4_r1.
The host machine is Ubuntu 12.10 amd64.

Is this problem results from the incorrect environment I used?
During compilation, because I fail to compile it by just following the 
instructions in the Wiki page. I made the following modifications:
1. I added -m32 to the compilation parameters for DalvikInstructionTracer for 
both gcc and g++.
2. I commented out the gthread-2.0 checking and usage in android-configure.sh

Thank you.

Original issue reported on code.google.com by icandoit...@gmail.com on 28 Feb 2013 at 12:47

[GoogleCodeExporter]

In the wiki page for DroidScope, it seems that we should use 32-bit OS to build 
it. But when building the Android from source, it will prompt that the Android 
source must be built on a 64-bit OS. There're many resource on the Internet 
telling how to build Android on a 32-bit OS. Should I apply them to build it on 
a 32-bit system? Or, should I build it on a 64-bit OS instead?

In the wiki page, it says that we should use Android Gingerbread. Could you 
tell me the exact version number I should use? (2.3.?)

I'm trying to figure out whether the problem I reported is the result of my 
incorrect environment.

Original comment by icandoit...@gmail.com on 4 Mar 2013 at 2:51

[GoogleCodeExporter]

Sorry that I should have posted the problem at the forum.
This issue can be ignored or deleted.

Original comment by icandoit...@gmail.com on 14 Mar 2013 at 3:01