On Sun, Feb 17, 2002 at 11:57:30PM -0500, Nathan Conrad wrote: > Hello, > > I've been using gcj to compile various java applets that I have > written. I've tried to use gdb (and ddd) to debug these programs, but > I have found that there are really long waits after certain commands > (such as run). I've had no problem with debugging C programs. I have > used the following command to compile my java application: > > $ gcj *.java -o test --main=Server -g > > And to debug it: > > $ gdb test > GNU gdb 5.1 > Copyright 2001 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "powerpc-linux"... > (gdb) run 9999 > Starting program: /home/conrad/smtp/test > [New Thread 1024 (LWP 25766)] > > <<<<At this point about 11 seconds pass by>>>> > > [New Thread 2049 (LWP 25769)] > [New Thread 1026 (LWP 25770)] > Server must have exactly one arg. > > Program exited normally. > (gdb) > > When run from the command line without gdb, the `test' command will be > run almost instantaneously. The step command takes a few seconds per > line. Also, when I run a backtrace (bt command), it takes about a > second for each line to appear. > > I'm using a 400 MHz PowerMac G4 with gdb 5.1-1 and gcj 3.0.4-2. Is > there any way to get rid of these delays? Has anyone else seen this > problem?
Welcome to thread support. It's very slow :) Is there actually no output at all during the pause? If so, and you have a testcase for me, I'll gladly try to make it go faster. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer
