« previous next »
Pages: 1 2 3 [All]   Go Down

Author Topic: The 26 July 2006 build is out.  (Read 36226 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5491
The 26 July 2006 build is out.
« on: July 26, 2006, 07:52:18 pm »
Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

A link to the unicode windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw26u_gcc_cb_wx2.6.3p2.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10.7z

For support of ansi builds, a link to the ansi windows wxWidget dll (2.6.2) for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw26_gcc_cb.7z

The 26 July 2006 build is out.
  - Windows : http://prdownload.berlios.de/codeblocks/CB_20060726_rev2786_win32.7z
  - Linux :
         http://prdownload.berlios.de/codeblocks/CB_20060726_rev2786_Ubuntu6.06.deb
         http://prdownload.berlios.de/codeblocks/CB_20060726_rev2786_fc4+5.rpm


Resolved Fixed:

  • ogre wizard: fixed several issues to work with recent OGRE SDK
  • wishlist.xml typo fixed [Patch #1234]

Regressions/Confirmed/Annoying/Common bugs:

  • toolbar-images-not-changing-state (is a wx problem/Win XP problem)
  • there are several issues with Code Completion (is being redesigned : work in progress)
  • menu items with icon not correctly aligned (since wx263)

« Last Edit: July 26, 2006, 10:00:14 pm by killerbot »
Logged

sethjackson

  • Guest
Re: The 26 July 2006 build is out.
« Reply #1 on: July 26, 2006, 08:54:10 pm »
EDIT:

Link removed.
« Last Edit: August 09, 2006, 08:28:29 pm by sethjackson »
Logged

Offline jpaterso

  • Multiple posting newcomer
  • *
  • Posts: 57
Re: The 26 July 2006 build is out.
« Reply #2 on: July 27, 2006, 06:04:29 am »
I'm getting crashes pretty much every time I close Code::Blocks. Is anyone else experiencing this?
Logged

Offline nix_BB

  • Multiple posting newcomer
  • *
  • Posts: 33
Re: The 26 July 2006 build is out.
« Reply #3 on: July 27, 2006, 08:49:04 am »
Nope, no crashes. (WinXP Pro with this nightly.)

If you gave some more info we might be able to help.

What OS are you running C::B on?
Did you follow the correct Installation procedure? (http://forums.codeblocks.org/index.php?topic=3232.0)
Which compiler toolset are you using?
etc.
Logged

agent007se

  • Guest
Re: The 26 July 2006 build is out.
« Reply #4 on: July 27, 2006, 09:46:33 am »
Quote from: jpaterso on July 27, 2006, 06:04:29 am
I'm getting crashes pretty much every time I close Code::Blocks. Is anyone else experiencing this?

Please take a screenshot because I'm getting to some craches when I close it!
Logged

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5491
Re: The 26 July 2006 build is out.
« Reply #5 on: July 27, 2006, 09:59:04 am »
for those having the crashes, disable the codecompletion plug-in (Plugins -> Manage plug-ins : uncheck it) and see if you still have those crashes. Please report back, thanks.
Logged

agent007se

  • Guest
Re: The 26 July 2006 build is out.
« Reply #6 on: July 27, 2006, 10:01:47 am »
The crashes still remain... (just tried now !) (the application crash at address 100, I posted a screenshot but all have ignored me... thinking that I can program but not installing a zip file :shock:) !
Logged

Offline jpaterso

  • Multiple posting newcomer
  • *
  • Posts: 57
Re: The 26 July 2006 build is out.
« Reply #7 on: July 27, 2006, 10:05:02 am »
I'm running Code::Blocks on Windows XP Pro, along with Mingw32. I followed the instructions when installing the nightly.
The crash is quite often at address 100, but sometimes not.

Disabling plugins doesn't seem to work: as soon as I re-launch Code::Blocks, the plugins load anyway.
Logged

agent007se

  • Guest
Re: The 26 July 2006 build is out.
« Reply #8 on: July 27, 2006, 10:07:09 am »
Quote from: jpaterso on July 27, 2006, 10:05:02 am
I'm running Code::Blocks on Windows XP Pro, along with Mingw32. I followed the instructions when installing the nightly.
The crash is quite often at address 100, but sometimes not.

Disabling plugins doesn't seem to work: as soon as I re-launch Code::Blocks, the plugins load anyway.

That's it !
Logged

Offline jpaterso

  • Multiple posting newcomer
  • *
  • Posts: 57
Re: The 26 July 2006 build is out.
« Reply #9 on: July 27, 2006, 10:11:25 am »
I deleted the files in Application Data\CodeBlocks, which seems to temporarily (until I use C::B around 4 times) fix the problem. I unloaded the CodeCompletion plugin there, but it doesn't seem to fix the problem.
Logged

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5491
Re: The 26 July 2006 build is out.
« Reply #10 on: July 27, 2006, 10:15:14 am »
Quote from: agent007se on July 27, 2006, 10:07:09 am
Quote from: jpaterso on July 27, 2006, 10:05:02 am
I'm running Code::Blocks on Windows XP Pro, along with Mingw32. I followed the instructions when installing the nightly.
The crash is quite often at address 100, but sometimes not.

Disabling plugins doesn't seem to work: as soon as I re-launch Code::Blocks, the plugins load anyway.

That's it !
:shock: :shock: :shock:

How did you disable them ??
Logged

Offline jpaterso

  • Multiple posting newcomer
  • *
  • Posts: 57
Re: The 26 July 2006 build is out.
« Reply #11 on: July 27, 2006, 11:42:41 am »
Using Plugins->Manage Plugins->Untick
Logged

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5491
Re: The 26 July 2006 build is out.
« Reply #12 on: July 27, 2006, 11:56:04 am »
and the next time you have started CB they are ticked again ??
Logged

rastik

  • Guest
Re: The 26 July 2006 build is out.
« Reply #13 on: July 27, 2006, 12:36:18 pm »
Hi,
I'm enclosing screenshot of the error. Clicking on Retry gives same message, Ignore gives message again with address increased by 2, Abort starts my debugger.

This how can I simulate this (with this build and every one released for approx. a week):
- Delete everythink in Application Data\codeblocks. C::B starts fine, close fine.
- Start C::B, open project, close C::B - everythink OK, can be tried many times.
- Start C::B, open project, set envirnoment to open last workspace (not default), close C::B.
- Start C::B, project is opened, close C::B - you'll get this error. Even when I change setting back to blank workspace, it won't be saved, C::B crashes first.
- If I set <BLANK_WORKSPACE bool="1" /> in default.conf, C::B gets ok.


[attachment deleted by admin]
Logged

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5491
Re: The 26 July 2006 build is out.
« Reply #14 on: July 27, 2006, 01:11:07 pm »
Quote
Start C::B, open project, set envirnoment to open last workspace (not default), close C::B.
???? how
Logged

rastik

  • Guest
Re: The 26 July 2006 build is out.
« Reply #15 on: July 27, 2006, 01:41:46 pm »
Quote from: killerbot on July 27, 2006, 01:11:07 pm
Quote
Start C::B, open project, set envirnoment to open last workspace (not default), close C::B.
???? how
Settings -> Environment -> General settings -> On application start-up
Sorry, it was meant "open default workspace (not blank)".
Logged

Offline Defender

  • Multiple posting newcomer
  • *
  • Posts: 49
Re: The 26 July 2006 build is out.
« Reply #16 on: July 27, 2006, 01:44:00 pm »
Quote from: rastik on July 27, 2006, 12:36:18 pm
Hi,
I'm enclosing screenshot of the error. Clicking on Retry gives same message, Ignore gives message again with address increased by 2, Abort starts my debugger.

This how can I simulate this (with this build and every one released for approx. a week):
- Delete everythink in Application Data\codeblocks. C::B starts fine, close fine.
- Start C::B, open project, close C::B - everythink OK, can be tried many times.
- Start C::B, open project, set envirnoment to open last workspace (not default), close C::B.
- Start C::B, project is opened, close C::B - you'll get this error. Even when I change setting back to blank workspace, it won't be saved, C::B crashes first.
- If I set <BLANK_WORKSPACE bool="1" /> in default.conf, C::B gets ok.

Maybe there is something wrong with your project file. Could you post it here? Or try it with another project in the workspace.
Logged

rastik

  • Guest
Re: The 26 July 2006 build is out.
« Reply #17 on: July 27, 2006, 01:53:29 pm »
Quote from: Defender on July 27, 2006, 01:44:00 pm
Maybe there is something wrong with your project file. Could you post it here? Or try it with another project in the workspace.
Posting my project file (renamed cbp to txt).

[attachment deleted by admin]
Logged

Offline Defender

  • Multiple posting newcomer
  • *
  • Posts: 49
Re: The 26 July 2006 build is out.
« Reply #18 on: July 27, 2006, 02:00:18 pm »
Quote from: rastik on July 27, 2006, 01:53:29 pm
Posting my project file (renamed cbp to txt).
Hmmm... for me it works fine (without the files). And I also don't see anything strange in your project :?
Logged

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5491
Re: The 26 July 2006 build is out.
« Reply #19 on: July 27, 2006, 02:12:40 pm »
could you try all of these

1) disable code completion plug-in, try again

in addition

2) remove all your sources from the project, try again

in case it works now ,ad some sources and try again

I don't think it has anything to do with the sources, but just to be sure.
Logged

Offline JPlaroche

  • Multiple posting newcomer
  • *
  • Posts: 29
    • OMBREBLEU
Re: The 26 July 2006 build is out.
« Reply #20 on: July 27, 2006, 02:17:19 pm »
Quote from: killerbot on July 27, 2006, 01:11:07 pm
Quote
Start C::B, open project, set envirnoment to open last workspace (not default), close C::B.
???? how

Hello, excuzez name English. 

why i must deactivate "keyboard shortcuts v0.4.22"


*****************************************************
a partir du 19 juillet

je ne peut plus activer le plugins keybinder
et en meme temps activer le " workspace"

si j'active les 2 en meme temps  il y a une erreur
*****************************************************
has to leave July 19

I more cannot activate the plugins keybinder and in meme times to activate the "workspace"

 if I activate the 2 in meme times there is an error

 

thank-you for the response
version  2786
« Last Edit: July 27, 2006, 02:48:11 pm by JPlaroche »
Logged
chef de projet MASTER (AS400  RPGILE  C   and SYTEM)

student c++ and wxwidgets for validation acquis (Jean-Pierre) wxformbuilder

agent007se

  • Guest
Re: The 26 July 2006 build is out.
« Reply #21 on: July 27, 2006, 02:55:43 pm »


I'm having the same error. I'll do some tests to see if I can help (i.e.: trying to create a new project and adding only one file.. two... and so on...)

  • If I close the project and the workspace (WP) then I can quit without problems.
  • I created a new project with GUI & Qt like options... (with default config).
  • I have no problem when closing C::B.

I think I figured out the "problem". It seems to be an incompatibility with the olds cbp files (I created mine with the 1rc2). Is it possible ?

Modification:
When closing (ok) relaunching and closing the error message came back !
Modification2:
I can reproduce it with a new project (this time a simple console project)
Modification3:
When re-opening my initial project (the one which I'm used to "work") :
« Last Edit: July 27, 2006, 03:14:25 pm by agent007se »
Logged

Offline orefa

  • Multiple posting newcomer
  • *
  • Posts: 102
Re: The 26 July 2006 build is out.
« Reply #22 on: July 27, 2006, 03:15:45 pm »
I also have this problem under Windows 2000 SP4. I didn't report it before since it occurs so regularly that I thought everyone including developpers were also experiencing the same thing and would attend to it in time. Task Manager shows that the codeblock process doesn't terminate immediately when the application closes, but a few seconds later Dr. Mingw pops up with this report:

Code
codeblocks.exe caused an Access Violation at location 00000064 Reading from location 00000064.

Registers:
eax=00000064 ebx=0121f1c0 ecx=00000001 edx=02ea4da0 esi=004c2910 edi=0022f0b0
eip=00000064 esp=0022ea4c ebp=0022ea68 iopl=0         nv up ei pl nz ac po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00000216

Call stack:
00000064
6298410A  keybinder.dll:6298410A
629A933B  keybinder.dll:629A933B  PluginSDKVersion
62991584  keybinder.dll:62991584  PluginSDKVersion
00538735  codeblocks.dll:00538735  _ZN8cbPlugin7ReleaseEb
005EC708  codeblocks.dll:005EC708  _ZN13PluginManager16UnloadAllPluginsEv
005EA43A  codeblocks.dll:005EA43A  _ZN13PluginManagerD0Ev
006D6394  codeblocks.dll:006D6394  _ZN3MgrI13PluginManagerE4FreeEv
005C841A  codeblocks.dll:005C841A  _ZN7Manager8ShutdownEv
00433645  codeblocks.exe:00433645
61A6A9C8  wxmsw26u_gcc_cb.dll:61A6A9C8  _ZN12wxEvtHandler21ProcessEventIfMatchesERK21wxEventTableEntryBasePS_R7wxEvent
61A6AD8C  wxmsw26u_gcc_cb.dll:61A6AD8C  _ZN16wxEventHashTable11HandleEventER7wxEventP12wxEvtHandler
61A6BD69  wxmsw26u_gcc_cb.dll:61A6BD69  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61BC8E33  wxmsw26u_gcc_cb.dll:61BC8E33  _ZN12wxWindowBase5CloseEb
61AF90C7  wxmsw26u_gcc_cb.dll:61AF90C7  _ZN7wxFrame13MSWWindowProcEjjl
61ACD8C0  wxmsw26u_gcc_cb.dll:61ACD8C0  _Z9wxWndProcP6HWND__jjl@16
77E4158F  USER32.dll:77E4158F  IsCharAlphaNumericW
77E3C19D  USER32.dll:77E3C19D  DdeQueryStringA
77E3C1CA  USER32.dll:77E3C1CA  DdeQueryStringA
77F91BAF  ntdll.dll:77F91BAF  NtOpenProcessToken
77E3C159  USER32.dll:77E3C159  DdeQueryStringA
61AD4A5C  wxmsw26u_gcc_cb.dll:61AD4A5C  _ZN8wxWindow13MSWWindowProcEjjl
61AF8F0A  wxmsw26u_gcc_cb.dll:61AF8F0A  _ZN7wxFrame13MSWWindowProcEjjl
61ACD8C0  wxmsw26u_gcc_cb.dll:61ACD8C0  _Z9wxWndProcP6HWND__jjl@16
77E4158F  USER32.dll:77E4158F  IsCharAlphaNumericW
77E3C19D  USER32.dll:77E3C19D  DdeQueryStringA
77E3C1CA  USER32.dll:77E3C1CA  DdeQueryStringA
77F91BAF  ntdll.dll:77F91BAF  NtOpenProcessToken
77E3C159  USER32.dll:77E3C159  DdeQueryStringA
61AD4A5C  wxmsw26u_gcc_cb.dll:61AD4A5C  _ZN8wxWindow13MSWWindowProcEjjl
61AF8F0A  wxmsw26u_gcc_cb.dll:61AF8F0A  _ZN7wxFrame13MSWWindowProcEjjl
61ACD8C0  wxmsw26u_gcc_cb.dll:61ACD8C0  _Z9wxWndProcP6HWND__jjl@16
77E4158F  USER32.dll:77E4158F  IsCharAlphaNumericW
77E41DC9  USER32.dll:77E41DC9  IsCharAlphaNumericW
77E41E7E  USER32.dll:77E41E7E  IsCharAlphaNumericW
61AAD284  wxmsw26u_gcc_cb.dll:61AAD284  _ZN11wxEventLoop8DispatchEv
61AAD020  wxmsw26u_gcc_cb.dll:61AAD020  _ZN11wxEventLoop3RunEv
61B46D7E  wxmsw26u_gcc_cb.dll:61B46D7E  _ZN9wxAppBase8MainLoopEv
004046E4  codeblocks.exe:004046E4
61A03C97  wxmsw26u_gcc_cb.dll:61A03C97  _Z14wxUninitializev
61A73C9A  wxmsw26u_gcc_cb.dll:61A73C9A  _Z7wxEntryP11HINSTANCE__S0_Pci
004014D8  codeblocks.exe:004014D8
004684EA  codeblocks.exe:004684EA
00401237  codeblocks.exe:00401237
004012A8  codeblocks.exe:004012A8
7C598989  KERNEL32.dll:7C598989  BaseAttachCompleteThunk

After reading the suggestions here I went through this process (I only use the default workspace and a few related projects):

1. Deactivated all plugins: no change.
2. Deleted all but one test project from the workspace: no change.
3. Deleted all source files from the remaining project: no change.
4. Deleted the last project from the default workspace: situation resolved, no error and the codeblocks process terminates immediately as seen from Task Manager.
5. Restored the last (empty) project: still closing normally, no error.
6. Added one source to the project: still closing normally, no error.
7. Restored other projects: it's baaa-ack! Errors are the same but a few values are different so I'm posting this new Dr. Mingw report again.

Code
codeblocks.exe caused an Access Violation at location 00000064 Reading from location 00000064.

Registers:
eax=00000064 ebx=0121f1c0 ecx=00000001 edx=02e9cb28 esi=004c2910 edi=0022f0b0
eip=00000064 esp=0022ea4c ebp=0022ea68 iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00000206

Call stack:
00000064
6298410A  keybinder.dll:6298410A
629A933B  keybinder.dll:629A933B  PluginSDKVersion
62991584  keybinder.dll:62991584  PluginSDKVersion
00538735  codeblocks.dll:00538735  _ZN8cbPlugin7ReleaseEb
005EC708  codeblocks.dll:005EC708  _ZN13PluginManager16UnloadAllPluginsEv
005EA43A  codeblocks.dll:005EA43A  _ZN13PluginManagerD0Ev
006D6394  codeblocks.dll:006D6394  _ZN3MgrI13PluginManagerE4FreeEv
005C841A  codeblocks.dll:005C841A  _ZN7Manager8ShutdownEv
00433645  codeblocks.exe:00433645
61A6A9C8  wxmsw26u_gcc_cb.dll:61A6A9C8  _ZN12wxEvtHandler21ProcessEventIfMatchesERK21wxEventTableEntryBasePS_R7wxEvent
61A6AD8C  wxmsw26u_gcc_cb.dll:61A6AD8C  _ZN16wxEventHashTable11HandleEventER7wxEventP12wxEvtHandler
61A6BD69  wxmsw26u_gcc_cb.dll:61A6BD69  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61A6BD09  wxmsw26u_gcc_cb.dll:61A6BD09  _ZN12wxEvtHandler12ProcessEventER7wxEvent
61BC8E33  wxmsw26u_gcc_cb.dll:61BC8E33  _ZN12wxWindowBase5CloseEb
61AF90C7  wxmsw26u_gcc_cb.dll:61AF90C7  _ZN7wxFrame13MSWWindowProcEjjl
61ACD8C0  wxmsw26u_gcc_cb.dll:61ACD8C0  _Z9wxWndProcP6HWND__jjl@16
77E4158F  USER32.dll:77E4158F  IsCharAlphaNumericW
77E3C19D  USER32.dll:77E3C19D  DdeQueryStringA
77E3C1CA  USER32.dll:77E3C1CA  DdeQueryStringA
77F91BAF  ntdll.dll:77F91BAF  NtOpenProcessToken
77E3C159  USER32.dll:77E3C159  DdeQueryStringA
61AD4A5C  wxmsw26u_gcc_cb.dll:61AD4A5C  _ZN8wxWindow13MSWWindowProcEjjl
61AF8F0A  wxmsw26u_gcc_cb.dll:61AF8F0A  _ZN7wxFrame13MSWWindowProcEjjl
61ACD8C0  wxmsw26u_gcc_cb.dll:61ACD8C0  _Z9wxWndProcP6HWND__jjl@16
77E4158F  USER32.dll:77E4158F  IsCharAlphaNumericW
77E3C19D  USER32.dll:77E3C19D  DdeQueryStringA
77E3C1CA  USER32.dll:77E3C1CA  DdeQueryStringA
77F91BAF  ntdll.dll:77F91BAF  NtOpenProcessToken
77E3C159  USER32.dll:77E3C159  DdeQueryStringA
61AD4A5C  wxmsw26u_gcc_cb.dll:61AD4A5C  _ZN8wxWindow13MSWWindowProcEjjl
61AF8F0A  wxmsw26u_gcc_cb.dll:61AF8F0A  _ZN7wxFrame13MSWWindowProcEjjl
61ACD8C0  wxmsw26u_gcc_cb.dll:61ACD8C0  _Z9wxWndProcP6HWND__jjl@16
77E4158F  USER32.dll:77E4158F  IsCharAlphaNumericW
77E41DC9  USER32.dll:77E41DC9  IsCharAlphaNumericW
77E41E7E  USER32.dll:77E41E7E  IsCharAlphaNumericW
61AAD284  wxmsw26u_gcc_cb.dll:61AAD284  _ZN11wxEventLoop8DispatchEv
61AAD020  wxmsw26u_gcc_cb.dll:61AAD020  _ZN11wxEventLoop3RunEv
61B46D7E  wxmsw26u_gcc_cb.dll:61B46D7E  _ZN9wxAppBase8MainLoopEv
004046E4  codeblocks.exe:004046E4
61A03C97  wxmsw26u_gcc_cb.dll:61A03C97  _Z14wxUninitializev
61A73C9A  wxmsw26u_gcc_cb.dll:61A73C9A  _Z7wxEntryP11HINSTANCE__S0_Pci
004014D8  codeblocks.exe:004014D8
004684EA  codeblocks.exe:004684EA
00401237  codeblocks.exe:00401237
004012A8  codeblocks.exe:004012A8
7C598989  KERNEL32.dll:7C598989  BaseAttachCompleteThunk

Hope this helps pinpoint the bug.

Logged

agent007se

  • Guest
Re: The 26 July 2006 build is out.
« Reply #23 on: July 27, 2006, 03:25:45 pm »
And for the last time, disabling the Code completion does not change anything (in manage plugin : unchecked and in the editor options disabled) :D.

But good luck to find the bug !

(I'm under WinXP SP1)
Logged

Offline jomabrueloe

  • Multiple posting newcomer
  • *
  • Posts: 10
Re: The 26 July 2006 build is out.
« Reply #24 on: July 27, 2006, 04:01:37 pm »
Hi,

I'm getting the same thing each time I close Code::Blocks since nightly of 18th of July (working under XP SP2). I tried several things with the configuration (no key bindings, no user colors, no splash screen...), but only in a completely unchanged config, the error seems to vanish. :?

Greetings

Jo

Logged

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5491
Re: The 26 July 2006 build is out.
« Reply #25 on: July 27, 2006, 04:06:43 pm »
extremey weird. What I am gonna do this evening is provide a nightly which contains all the debug info, so your download will be bigger. But then the RPT file will probably contain more info.

So sad I don't have this crash :-(
Logged

Offline k1mgy

  • Multiple posting newcomer
  • *
  • Posts: 64
Re: The 26 July 2006 build is out.
« Reply #26 on: July 27, 2006, 04:31:52 pm »
On my windows xp workstation, (and for 1,000 years) I've used the number keypad for keyboard navigation.  It's been a few months since I've updated Code::Blocks, but decided it was time :)

Now the navigation keys on the number pad no longer function.  Yes, I don't have numlock pressed :), but the arrow pad to the left of the number pad does.

I can't change the wiring in my brain to deal with this.  So what, if anything, can I do in Code::Blocks to bring back these keys?  (I checked all the configuration settings that seemed to faintly apply, with no joy).

Thanks!

Logged

Offline orefa

  • Multiple posting newcomer
  • *
  • Posts: 102
Re: The 26 July 2006 build is out.
« Reply #27 on: July 27, 2006, 05:11:39 pm »
I seem to have fixed the problem on my system after a bit of poking around.

I should first mention that I didn't properly check the plugin status in my previous tests (reply #22 above) and after turning them all off, since CB produced an error and did not shut down correctly, they were all checked again at the next test. I had not noticed that.

I tried closing the whole workspace and turning off the plug-ins before shutting down but that didn't help.

Next, I deleted all projects but retained the workspace: that worked. Code::Blocks shut down correctly and all plug-ins remained disabled at the next run.

After this I restored the projects and CB continues to shut down without error. Then I restored the plug-ins progressively and so far so good, all projects and all plug-ins are active and the shut-down problem is gone.

I leave it to the developpers to figure out what this means, but meanwhile this has been a work-around solution that worked for me. Try it and see if it also works for those who also have that error.

------

EDIT: This is fifteen minutes later. The problem is back again. Oh well...

------
« Last Edit: July 27, 2006, 05:28:16 pm by orefa »
Logged

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5491
Re: The 26 July 2006 build is out.
« Reply #28 on: July 27, 2006, 05:34:38 pm »
plug-ins to try to disable (start CB without any project so you can surely close it ;-) without crashing).
 - codecompletion
 - keybinder

Logged

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5491
Re: The 26 July 2006 build is out.
« Reply #29 on: July 27, 2006, 05:35:29 pm »
Quote from: k1mgy on July 27, 2006, 04:31:52 pm
On my windows xp workstation, (and for 1,000 years) I've used the number keypad for keyboard navigation.  It's been a few months since I've updated Code::Blocks, but decided it was time :)

Now the navigation keys on the number pad no longer function.  Yes, I don't have numlock pressed :), but the arrow pad to the left of the number pad does.

I can't change the wiring in my brain to deal with this.  So what, if anything, can I do in Code::Blocks to bring back these keys?  (I checked all the configuration settings that seemed to faintly apply, with no joy).

Thanks!



yes we are ware of this problem, but still need to search for it. It seems it's already in for a few months.
Which version did you use just before your update ???
Logged

Offline k1mgy

  • Multiple posting newcomer
  • *
  • Posts: 64
Re: The 26 July 2006 build is out.
« Reply #30 on: July 27, 2006, 05:41:10 pm »
Verion prior was code blocks exe dated 5/1/2006.

Sorry, don't have a build number for you.
Logged

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5491
Re: The 26 July 2006 build is out.
« Reply #31 on: July 27, 2006, 05:48:39 pm »
Quote from: k1mgy on July 27, 2006, 05:41:10 pm
Verion prior was code blocks exe dated 5/1/2006.

Sorry, don't have a build number for you.

damn : january, that's the bginning of the nightly builds :-(
Logged

Offline orefa

  • Multiple posting newcomer
  • *
  • Posts: 102
Re: The 26 July 2006 build is out.
« Reply #32 on: July 27, 2006, 05:51:14 pm »
Quote from: killerbot on July 27, 2006, 05:34:38 pm
plug-ins to try to disable (start CB without any project so you can surely close it ;-) without crashing).
 - codecompletion
 - keybinder

Ok, I tried both and then each one in turn. Disabling the "Keyboard Shortcuts" plug-in solves it. The "Code Completion" plug-in doesn't seem to be involved here, it is turned on right now and causes no problem.
Logged

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5491
Re: The 26 July 2006 build is out.
« Reply #33 on: July 27, 2006, 05:52:56 pm »
Quote from: orefa on July 27, 2006, 05:51:14 pm
Quote from: killerbot on July 27, 2006, 05:34:38 pm
plug-ins to try to disable (start CB without any project so you can surely close it ;-) without crashing).
 - codecompletion
 - keybinder

Ok, I tried both and then each one in turn. Disabling the "Keyboard Shortcuts" plug-in solves it. The "Code Completion" plug-in doesn't seem to be involved here, it is turned on right now and causes no problem.

This is wht I suspected, things started to go wrong last week when the keybinder got updated. Remains strange I don't have it :-(

Do you have bindings you have defined yourself, or did you have the plug-in active because it comes with CB ;-)

[EDIT] : 27 nightly DEBUG BUILD nearly uploaded --> let it crash and look at the rpt ;-)
Logged

Offline k1mgy

  • Multiple posting newcomer
  • *
  • Posts: 64
Re: The 26 July 2006 build is out.
« Reply #34 on: July 27, 2006, 06:44:51 pm »
Not certain you folks are addressing the issue with the keypad or another in the thred.

I disabled the code completion and keyboard plugins and no difference. 

I get a warning each time I load a file:

pluginwizard.dll
projectwizard.dll

not loaded.

Maybe this is a mingw issue?
Logged

nu-kinetix

  • Guest
Re: The 26 July 2006 build is out.
« Reply #35 on: July 27, 2006, 07:37:18 pm »
Quote
This is wht I suspected, things started to go wrong last week when the keybinder got updated. Remains strange I don't have it

Do you have bindings you have defined yourself, or did you have the plug-in active because it comes with CB
I've had the same problem for the past 2-3 weeks as well.

I never defined bindings myself but the easy solution (i.e. stops CB from crashing upon exit) is to disable (or altogether delete!) the keybinder.dll in the plugins folder. That always seems to work, so obviously the problem is in there somewhere :)
Logged

Offline orefa

  • Multiple posting newcomer
  • *
  • Posts: 102
Re: The 26 July 2006 build is out.
« Reply #36 on: July 27, 2006, 07:44:26 pm »
Quote from: killerbot on July 27, 2006, 05:52:56 pm
Do you have bindings you have defined yourself, or did you have the plug-in active because it comes with CB ;-)

I almost forgot to answer your question...

I have defined nothing myself either. I don't know what most of these plug-ins do so I don't touch them, leave everything as is, try to keep out of trouble, mind my own business, ask no question, keep to myself, fade to black...  8)
Logged

rastik

  • Guest
Re: The 26 July 2006 build is out.
« Reply #37 on: July 27, 2006, 07:47:42 pm »
Quote from: nu-kinetix on July 27, 2006, 07:37:18 pm
I never defined bindings myself but the easy solution (i.e. stops CB from crashing upon exit) is to disable (or altogether delete!) the keybinder.dll in the plugins folder. That always seems to work, so obviously the problem is in there somewhere :)
Same for me - never used key bindings and deleting keybinder.dll solves the problem. When new nightly is out, I'll let it crash and until the problem is solved I'm happy without this plug-in.
Logged

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5491
Re: The 26 July 2006 build is out.
« Reply #38 on: July 27, 2006, 10:55:30 pm »
Quote from: k1mgy on July 27, 2006, 06:44:51 pm
Not certain you folks are addressing the issue with the keypad or another in the thred.

I disabled the code completion and keyboard plugins and no difference. 

I get a warning each time I load a file:

pluginwizard.dll
projectwizard.dll

not loaded.

Maybe this is a mingw issue?


keypad issue will be investigated later, focusing first on the crash problems.
However pluginwizar.dll and projectwizard.dll are no longer needed. So in case you are using a recent nightly build (say from the last 2 weeks) remove those 2 dll's (they should be in <CodeBlocks-dir>\share\CodeBlocks\plugins).
Or install your nightly in a clean empty directory since they are no longer in the nightly build zip file.

Please give feedback if your warnings about those 2 dll's are gone (just to be sure).
Logged

Offline k1mgy

  • Multiple posting newcomer
  • *
  • Posts: 64
Re: The 26 July 2006 build is out.
« Reply #39 on: July 27, 2006, 11:00:26 pm »
OK, I removed the two dll's and no more errors.  Also no crashing to report in any case.

Note that I am using the unicode dll.  Should I test using the other, or is the nightly only unicode compatible, or will it matter?

Logged

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5491
Re: The 26 July 2006 build is out.
« Reply #40 on: July 27, 2006, 11:07:40 pm »
(official)  nightly builds are unicode, from time to time an ansi builds is also provided, but people should use unicode build (unless you are on win 9x).

Some people are suffering from crashes, and the most recent crashes "seem" to disappear when keybinder is turned off.
Logged

Offline Pecan

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 2770
Re: The 26 July 2006 build is out.
« Reply #41 on: July 28, 2006, 04:38:19 am »
I'll revert keybinder when I get home tomorrow evening.

pecan
Logged
Pages: 1 2 3 [All]   Go Up
« previous next »