« previous next »
Pages: [1]   Go Down

Author Topic: gdb.exe eat 250M+ memory when debuging cb under cb  (Read 4543 times)

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 6077
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
gdb.exe eat 250M+ memory when debuging cb under cb
« on: September 26, 2009, 10:06:05 am »
I just find that when I debug codeblocks svn under codeblocks + TDM-GCC 4.4.0 + gdb6.8.

gdb.exe eat 250M memory :shock:.

If I can remember, this value was about 120M several months ago.


Is this a normal thing :D? 

Thanks.
Logged
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 blueshake

  • Regular
  • ***
  • Posts: 458
Re: gdb.exe eat 250M+ memory when debuging cb under cb
« Reply #1 on: September 27, 2009, 04:24:05 am »
I can confirm this issue.In the latest cb,when I debug cb codes,it always happened.
Logged
Keep low and hear the sadness of little dog.
I fall in love with a girl,but I don't dare to tell her.What should I do?

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9723
Re: gdb.exe eat 250M+ memory when debuging cb under cb
« Reply #2 on: September 27, 2009, 11:40:29 am »
Quote from: ollydbg on September 26, 2009, 10:06:05 am
If I can remember, this value was about 120M several months ago.
Keep in mind that for example as CC has improved it will therefore keep a lot more information in memory. So if you debug a big projects with a lot of symbols the memory footprint can increase, indeed.
Logged
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 6077
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: gdb.exe eat 250M+ memory when debuging cb under cb
« Reply #3 on: September 27, 2009, 05:12:07 pm »
@morten
I didn't agree with you. Because When I haven't open any project in the debugee(codeblocks), the gdb.exe has already reached 250M+.
I believe this is not caused by the new CC code.  :D Maybe, the linker is different.
Logged
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.
Pages: [1]   Go Up
« previous next »