Re: xxgdb or ddd
> Thank you for your reply:
> Firstly, at the command line I enter the following --> xxgdb gdbtst
> Following that, the 4 windows open and then close. In the window
> where I started the program I get Segmentation Violation. So I don't have
> an opportunity to do anything within the debugger.
Hmm, that really looks like something wrong with the debugger. As far
as I know both xxgdb and ddd use gdb as their underlying debugger. Can
you debug the program with gdb? Try to run `gdb gdbtst' and see if that
works (or run gdb and type `file gdbtst'). If this works, the problem
is in the graphical interface, if it doesn't, it is in gdb. You should
be able to see what versions of gdb, xxgdb and ddd you have typing
`dpkg -s <package>'. I have gdb 4.16-2 and xxgdb 1.12-6 which work OK.
> If I just start xxgdb and try to select the file to debug, following the
> selection of the file all the xxgdb window remove themselves from the
> The progam that I am running is a simple hello world C program
> which runs fine from the command line.
> With respect to the use of the`where' command, I am not familiar with
> that command. Can you tell me more.
If you stop a program in gdb (or ddd or xxgdb for that matter), or if
it crashes, the `where' command shows where the program is: in what
function, and called by what other function. If you have the source
available, you can see the exact source line with the list command.
E.L. Meijer (email@example.com) | tel. office +31 40 2472189
Eindhoven Univ. of Technology | tel. lab. +31 40 2475032
Lab. for Catalysis and Inorg. Chem. (TAK) | tel. fax +31 40 2455054
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .