From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: Error debugging Date: 14 Nov 2000 13:12:38 GMT Organization: Aachen University of Technology (RWTH) Lines: 18 Message-ID: <8urdo6$cf0$1@nets3.rz.RWTH-Aachen.DE> References: <8uprbl$cd9$1 AT venus DOT telepac DOT pt> <3A111EE4 DOT 6456EBDE AT ujf-grenoble DOT fr> <8ur78v$hnh$1 AT venus DOT telepac DOT pt> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 974207558 12768 137.226.32.75 (14 Nov 2000 13:12:38 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 14 Nov 2000 13:12:38 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Paulo J. Matos aka PDestroy wrote: > So, are you telling me that the problem is in my djgpp instalation? No. It's in the way you use the debugger. You didn't tell gdb what to 'list', so it's trying to list whatever it currently points at. Typing 'list' without any arguments is fine once you've started the program itself and it reached a breakpoint, or after a previous 'list' command. But for your situation, you should tell it what to list. E.g.: list main or list simul.c:123 to start listing at line 123 of simul.c -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.