- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
First, not sure if this is the correct forum, since this is a question about the debugger IDB rather than the compiler, but I didn't see any other forum that seems to be more appropriate (please point me to one if that's the case).
I am trying IDB for the first time after downloading the compiler suite 11.0.083. I downloaded the intel64 version, and my machine is AMD athlon 64 3000 running Fedora 10, 64 bit.
The problem is that IDB is really slow and barely responsive. Using "top", I see that the process "java" keeps using anywhere from 80% to 100%. My JRE comes with the distribution: openjdk-1.6.
Has anyone seen something like this before ? Is there a known problem with my configuration, or is there a workaround to this problem ?
Thanks for any help.
RDB
First, not sure if this is the correct forum, since this is a question about the debugger IDB rather than the compiler, but I didn't see any other forum that seems to be more appropriate (please point me to one if that's the case).
I am trying IDB for the first time after downloading the compiler suite 11.0.083. I downloaded the intel64 version, and my machine is AMD athlon 64 3000 running Fedora 10, 64 bit.
The problem is that IDB is really slow and barely responsive. Using "top", I see that the process "java" keeps using anywhere from 80% to 100%. My JRE comes with the distribution: openjdk-1.6.
Has anyone seen something like this before ? Is there a known problem with my configuration, or is there a workaround to this problem ?
Thanks for any help.
RDB
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As idb is a compiler component, this may be the best forum for this discussion.
I haven't used idb GUI sufficiently to make a judgment on how often java overhead becomes annoying, but I'm not surprised. Of course, Athlon-64 would not be a primary test platform, so it could be worse for you. It looks like you got the right JRE automatically.
Like it or not, the work-around which occurs to me would be the non-GUI version, idbc. You might have jobs where one or the other is more convenient. We often try gdb as well.
I haven't used idb GUI sufficiently to make a judgment on how often java overhead becomes annoying, but I'm not surprised. Of course, Athlon-64 would not be a primary test platform, so it could be worse for you. It looks like you got the right JRE automatically.
Like it or not, the work-around which occurs to me would be the non-GUI version, idbc. You might have jobs where one or the other is more convenient. We often try gdb as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi RDB,
in our validation environments and from other customer feedback your observation really is quite unusual. Although we don't officially validate against Fedora 10 just yet, I have personally used IDB on Fedora 10 a few times and not seen this type of behavior before. Something must be going wrong with the debug setup on your system. perhaps a conflict between the Java JRE and some other Java based install? ..... Could you provide us a bit more information about the workload (binary size, memory utilization, number of shared objects loaded at the same time) that you are trying to debug? Getting a more complete picture of your debug platform in terms of memory available and processor speed may be useful as well.
Lastly it may be worthwhile to install the original Java JRE from www.java.com. I think the Sun JRE is directly available through the Fedora RPM Manager.
Thanks, Rob
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page