Re: GDB debugger problem
On Apr 1, 4:57 pm, Christopher <cp...@austin.rr.com> wrote:
On Apr 1, 9:45 am, mohi <mohangupt...@gmail.com> wrote:
hello everyone,
i was debugging a simple program using gdb debugger and when in
function display
on the simple line
cout<<"this is the out put";
........
.......
.....
there was no output from the program and the gdb promp(gdb>)
also disappered from here on and after sometime it showed something
like
"the program recived signal SIGINT" or something like that
and also while running the program this few lines were not displayed
(im using fedora core 8 and was on g++ on command line)
can anyone please tell what was wrong with that.
Show more source. You have a segmentation fault in your code.
That would be SIGSEGV. Normally, SIGINT is generated by
control-C on the keyboard.
Since the poster didn't indicate what gdb commands he'd used
(not that that would be on topic here), it's impossible to say
what might be happening. One thing is clear, however: he didn't
ask for any output from the program, so it's not surprising that
he didn't get any. And of course, the gdb prompt only appears
when the program has stopped for some reason; if the program is
executing, gdb doesn't output a prompt.
--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34