News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

The 14 April 2012 build (7932) is out.

Started by killerbot, April 14, 2012, 12:25:59 PM

Previous topic - Next topic

ollydbg

Quote from: cacb on April 16, 2012, 11:11:03 PM
7932 has the lag
7925 appears to have the lag
7917 appears to have the lag
7452 no lag
7385 no lag
I do not have such lag.
QuoteWhen using 7392 it takes 10 seconds before I see anything in the build log window (i.e. that no rebuild is required) after pressing the toolbar build button. With the old nightly (7452), the respons is immediate.
In my Computer (WinXP, C::B nightly build 7932), the build log shows immediate after I press the toolbar button.
Did you use "debugger branch nightly" or "normal trunk nightly". Can you do some test to see from which nightly build version, the lag begins. Thanks.
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.

NilC

oBFusCATed,
7790 - no lags,
7918 (debugger brunch), 7917 (main brunch) - first builds with lags


vollkorn

Hi,

I'm new to windows and was looking for a nice alternative to MS Visual Studio 2010. So I wanted to try CB for the first time and installed the nightly 7932 as described in the first post of this thread on a Win7 64 bit machine. Then I chose the installed MSVC 2010 compiler, skipped the spellchecker installation and file association and tried to import a *.sln file. I said yes to using the default compiler and yes to import all settings, but then CB dies and I'm offered to close or debug the program. When starting the debugger I can't figure out much though b/c I don't have the sources installed.

How can I help debugging this problem?

Freem

You gave steps, but there is also the crash log which could help them.

MortenMacFly

Quote from: vollkorn on April 18, 2012, 10:48:25 AM
How can I help debugging this problem?
Provide a simple test case (i.e. a minimal MSVS project) to reproduce.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

vollkorn

In this post you can find the report file with three crashs and a test.sln I tried to open during the last crash.

MortenMacFly

Quote from: vollkorn on April 19, 2012, 09:54:04 AM
In this post you can find the report file with three crashs and a test.sln I tried to open during the last crash.
Having just the solution file is not enough, because there is nothing to import. Please provide a full minimal sample, including at least the project files. To try, please copy your solution / project / other files (step-by-step, as needed) into a new folder an try to import from there until C::B crashes, that provide exactly that full set of files (zipped) here.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

vollkorn

I deleted the debug folders and the SQL server's file to meet the space limit of this upload funciton.

[attachment deleted by admin]

vollkorn

Sorry, I forgot to mention: The crash occurs already with the test.sln only. No other files needed, but I included as much as possible just to make sure.

nenin

Not found any lags at 7932 and do not remember ones with DEBUGGER BRANCH. Now I use niXman mingw package (http://sourceforge.net/projects/mingwbuilds/), but similar situation was with TDM mingw + ollydbg gdb. Lags occurs when I try to view large STL containers.

oBFusCATed

Quote from: nenin on April 19, 2012, 04:05:36 PM
Lags occurs when I try to view large STL containers.
Explain please. What does it mean view?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

nenin

Quote from: oBFusCATed on April 19, 2012, 04:08:40 PM
Quote from: nenin on April 19, 2012, 04:05:36 PM
Lags occurs when I try to view large STL containers.
Explain please. What does it mean view?
"View" means "watch under debugger".   

oBFusCATed

OK, this is normal and it is unfixable at the moment.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

nenin

Quote from: oBFusCATed on April 19, 2012, 05:55:15 PM
OK, this is normal and it is unfixable at the moment.
I wonder if it possible to tune gdb to show, for example, first 100 elements in container by default.

oBFusCATed

You have to edit the python scripts or the stl-views.gdb script in C::B to do it.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]