On Sat, Oct 23, 1999 at 04:29:44PM -0500, kenneth m handzik wrote:
> Ok. Now where can i get an walkthrough of actually debugging between gdb,
> emacs and copilot/pose?
>
> Most any command i try just hangs the emacs menu entry.
>
> Also, response is very slow in loading and starting gdb. it takes anywhere
> from 15-25 seconds for the (gdb) prompt to come up or return after entering
> the target command.
>
> i'd like to hear from anybody who still uses this development environment.
I use gdb, but from the command line, not through emacs. I think most
of this information is still valid though.
After the target command returns, you can set breakpoints with the
break command. e.g. "break 123", "break filename.c:123" (where 123 is a
line number), "break functionname". You don't have to set a breakpoint;
the program will automatically break when an error dialog is about to be
shown. After setting breakpoints, type "continue". The program will
run until either an error occurs or control reaches a breakpoint, at
which time you are returned to the (gdb) prompt. Some commands useful
at this point:
print variablename - self-explanatory
step - execute the current line, tracing into function calls
next - execute the current line, skipping over function calls
up - move to a higher stack frame. if an error dialog occured, you
should use the up command a few times to get back to your code.
For more information on using gdb, try the help command in gdb or type
C-h i m "gdb" RET in emacs.
-Ben
--
Ben Darnell [EMAIL PROTECTED]
http://www4.ncsu.edu/~bgdarnel/thoughtstream/
