Author Topic: place for stdout output during debugging  (Read 4554 times)

Offline lehe

  • Multiple posting newcomer
  • *
  • Posts: 35
place for stdout output during debugging
« on: April 09, 2009, 04:52:56 am »
Hi,
I just found that during debugging in CB, the stdout put info that are supposed to appear on the console window changes to show in the "Debugger(debug)" window. I don't know what caused this change. Does someone know why and how to switch between these two ways?
Thanks!
« Last Edit: April 09, 2009, 05:02:18 am by lehe »

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 6077
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: place for stdout put during debugging
« Reply #1 on: April 09, 2009, 04:57:49 am »
really? Which OS? Which version?

In my windows, no situation as you mentioned. But if you are debugging a GUI program, the stdout may redirect to GDB output.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline lehe

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: place for stdout put during debugging
« Reply #2 on: April 09, 2009, 05:00:56 am »
A simple console program not involving GUI.
Under Ubuntu8.10.

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 6077
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: place for stdout put during debugging
« Reply #3 on: April 09, 2009, 05:54:29 am »
A simple console program not involving GUI.
Under Ubuntu8.10.
Oh, Sorry, I can't help any more, because I only use Windows XP. :(
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.