Re: GDB debugger problem
On Apr 1, 4:55 pm, "Victor Bazarov" <v.Abaza...@comAcast.net> wrote:
mohi wrote:
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.
Whatever is wrong with that, it has nothing to do with C++ language.
The fact that nothing was displayed probably does. At the very
least, his output isn't significant without a flush.
Consider asking in an appropriate gnu.* newsgroup or the
newsgroup for your platform.
While that's true too, I doubt that he'll get much help anywhere
with such a vague description.
FWIW: under Unix, SIGINT is normally what the program gets when
you enter control-C. Program errors more often result in
SIGSEGV or SIGBUS, or maybe SIGILL, SIGFPE or SIGSYS. But of
course, given an error wierd enough, just about anything can
happen.
--
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