Author Topic: The 22 May 2006 build is out.  (Read 14051 times)

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4291
    • Code::Blocks IDE
Re: The 22 May 2006 build is out.
« Reply #15 on: May 24, 2006, 10:09:13 am »
regarding gdb parsing I attach an example;

Thanks for the example. The fix is in SVN so expect it to appear in tonight's build.
Be patient!
This bug will be fixed soon...

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9604
Re: The 22 May 2006 build is out.
« Reply #16 on: May 24, 2006, 10:34:13 am »
Thanks for the example. The fix is in SVN so expect it to appear in tonight's build.
mandrav, your are the hero. I wonder if this also fixes this issue: http://forums.codeblocks.org/index.php?topic=2910.msg22996#msg22996 which caused me a headache at that time. I couldn't resolve it and then (:oops: shame on me! :oops:) forgot about it.
Well I guesss I have to do another build for today to figure that out... stay tuned... ;-)
With regards, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4291
    • Code::Blocks IDE
Re: The 22 May 2006 build is out.
« Reply #17 on: May 24, 2006, 10:52:38 am »
Thanks for the example. The fix is in SVN so expect it to appear in tonight's build.
mandrav, your are the hero. I wonder if this also fixes this issue: http://forums.codeblocks.org/index.php?topic=2910.msg22996#msg22996 which caused me a headache at that time. I couldn't resolve it and then (:oops: shame on me! :oops:) forgot about it.
Well I guesss I have to do another build for today to figure that out... stay tuned... ;-)
With regards, Morten.

This should be fixed since last week. I fixed it. But if you find any way to make it misbehave again, I 'd like to know it ;)
Be patient!
This bug will be fixed soon...