News:

The new Release 25.03 is out! You can download binaries for Windows and many major Linux distros here .

Main Menu

The 14 April 2012 build (7932) is out.

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

Previous topic - Next topic

cacb

Quote from: ollydbg on April 17, 2012, 05:25:39 AM
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.

Sorry, I have been away, ongoing family issue.  I have never used debugger branch, never built CB myself. Only downloaded pre-built nihgtlies, always main version which I presume is based on trunk.

MortenMacFly

Quote from: cacb on April 19, 2012, 08:21:34 PM
I have never used debugger branch, never built CB myself. Only downloaded pre-built nihgtlies, always main version which I presume is based on trunk.
The latest nightly is basically the debugger branch as it has been merged into trunk meanwhile.
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]

ollydbg

Quote from: nenin on April 19, 2012, 06:00:36 PM
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.
See:Why C::B over write gdb's set print element value?
And you can use:

set print elements 100

In your custom startup .gdb script file.
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.

nenin

#33
Quote from: ollydbg on April 20, 2012, 02:27:52 AM
See:Why C::B over write gdb's set print element value?
And you can use:

set print elements 100

In your custom startup .gdb script file.
Not works when I watch std::container.  :(
With array it works.

norbitheeviljester

I've installed this built on a few machines. To my surprise I can't seem to use the Watches window on one of them. I can't seem to get my head around to why is that. The Watch window is empty - It should show local variable and function arguments but it doesn't. I can add a watch manually - then the entire entry turns red.
I've tried doing this with multiple versions of nightly builts as well as mingws. It seems that on one of my machines I the Watches window just doesn't work.
It works fine on the normal Code::Blocks 10.5 though.
Any ideas?
I'm running windows 7 x64, copied all the dlls from the post, using MinGW attached to Code::Blocks 10.5 or MinGW 5.16.
the nightlies and the MinGW are in a path without spaces, the C::B 10.5 contains spaces in it's path - could this somehow be an issue?

oBFusCATed

Local variables and function arguments are not reimplemented in the new watches window, sorry...

The red entries in the watches window means that the value of the watch has just changed, this pretty usefull if you step through the code.
And the first time you add a watch it is red, but the values should be correct. Are they correct?
(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!]

kimp

#36
CB + TortoiseSVN: CB crashes when I choose project folder in File Explorer (win 7, Tortoise 1.7 build r22413)

Here is log:


Error occured on Friday, April 20, 2012 at 06:23:16.

D:\codeblocks\nightly\codeblocks.exe caused an Access Violation at location 63082ca2 in module D:\codeblocks\nightly\share\codeblocks\plugins\FileManager.dll Reading from location 00000000.

Registers:
eax=00000000 ebx=00000000 ecx=7ffde000 edx=00000000 esi=00000000 edi=03ce1580
eip=63082ca2 esp=0022f71c ebp=0022f7a4 iopl=0         nv up ei pl nz na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010202

Call stack:
63082CA2  D:\codeblocks\nightly\share\codeblocks\plugins\FileManager.dll:63082CA2
63082FBB  D:\codeblocks\nightly\share\codeblocks\plugins\FileManager.dll:63082FBB
6308C50E  D:\codeblocks\nightly\share\codeblocks\plugins\FileManager.dll:6308C50E
6CCC7670  D:\codeblocks\nightly\wxmsw28u_gcc_cb.dll:6CCC7670  _ZN12wxEvtHandler21ProcessEventIfMatchesERK21wxEventTableEntryBasePS_R7wxEvent
6CCC77A9  D:\codeblocks\nightly\wxmsw28u_gcc_cb.dll:6CCC77A9  _ZN16wxEventHashTable11HandleEventER7wxEventP12wxEvtHandler
6CCC7B74  D:\codeblocks\nightly\wxmsw28u_gcc_cb.dll:6CCC7B74  _ZN12wxEvtHandler12ProcessEventER7wxEvent
6CCC7528  D:\codeblocks\nightly\wxmsw28u_gcc_cb.dll:6CCC7528  _ZN12wxEvtHandler20ProcessPendingEventsEv
6CC417AE  D:\codeblocks\nightly\wxmsw28u_gcc_cb.dll:6CC417AE  _ZN12wxAppConsole20ProcessPendingEventsEv
6D05E549  D:\codeblocks\nightly\wxmsw28u_gcc_cb.dll:6D05E549  _ZN18wxIconLocationBaseC2ERK8wxString
757C7B45  C:\Windows\system32\USER32.dll:757C7B45  GetUserObjectInformationA
757D31EB  C:\Windows\system32\USER32.dll:757D31EB  GetClassNameW
757D4260  C:\Windows\system32\USER32.dll:757D4260  ChangeWindowMessageFilter
7725642E  C:\Windows\SYSTEM32\ntdll.dll:7725642E  KiUserCallbackDispatcher
6CCF569A  D:\codeblocks\nightly\wxmsw28u_gcc_cb.dll:6CCF569A  _ZN11wxEventLoop8DispatchEv
6CD8D518  D:\codeblocks\nightly\wxmsw28u_gcc_cb.dll:6CD8D518  _ZN17wxEventLoopManual3RunEv
6CD6BB19  D:\codeblocks\nightly\wxmsw28u_gcc_cb.dll:6CD6BB19  _ZN9wxAppBase8MainLoopEv
0044D016  D:\codeblocks\nightly\codeblocks.exe:0044D016
6CC73248  D:\codeblocks\nightly\wxmsw28u_gcc_cb.dll:6CC73248  _Z14wxUninitializev
6CCCD392  D:\codeblocks\nightly\wxmsw28u_gcc_cb.dll:6CCCD392  _Z7wxEntryP11HINSTANCE__S0_Pci
004492F9  D:\codeblocks\nightly\codeblocks.exe:004492F9
00487EA6  D:\codeblocks\nightly\codeblocks.exe:00487EA6
004010DB  D:\codeblocks\nightly\codeblocks.exe:004010DB
00401158  D:\codeblocks\nightly\codeblocks.exe:00401158
75991174  C:\Windows\system32\kernel32.dll:75991174  BaseThreadInitThunk
7726B3F5  C:\Windows\SYSTEM32\ntdll.dll:7726B3F5  RtlInitializeExceptionChain
7726B3C8  C:\Windows\SYSTEM32\ntdll.dll:7726B3C8  RtlInitializeExceptionChain



MortenMacFly

Quote from: kimp on April 22, 2012, 08:40:27 AM
CB + TortoiseSVN: CB crashes when I choose project folder in File Explorer (win 7, Tortoise 1.7 build r22413)
Shall we use our magic balls to know the steps to reproduce? Mine is broken, sorry.

Look: I have another tool, when I press a button in C::B it crashes - can you help me with that information provided? >:(
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]

kimp

I'm sorry. C::B crashes if "View->SVN decorators" is selected

nenin

#39
ollydbg, I found source of the problem. C::B after upgrades "lost" pyton gdb scripts. If  pyton gdb properly tuned, "set print elements 100" in config works.

Wyz

I confirm something strange with this nighlty. When opening large source files (> 10.000 lines) or switching from one to an other using the tabs it is very slow.
Latest build I'm using is 7789 and this doesn't occur.

oBFusCATed

Disable the TODO plugin and it will be fast again.
(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!]

Wyz


hooluupog

#43
Hi,
  I debug my code in  build (7932) but codeblocks freezed.

  std::vector<_int> out;
 std::vector<_int> in;
 in.resize(num.length());
 for(;i<num.length();++i)        // when debugger going into this line, codeblocks freezed.
 in[i] = num[i]-'0';
out.resize(num.length());

num was defined as a string with 100000 chars. I tried to shrink num into 10000 or so then it needed 2 minutes  to get the result. It is so slow to debug a large data.

oBFusCATed

hooluupog: Read few post about about "set print elements"
(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!]