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

Offline rastik

  • Single posting newcomer
  • *
  • Posts: 7
Re: The 26 July 2006 build is out.
« Reply #15 on: July 27, 2006, 01:41:46 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)".

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 »
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.

Offline rastik

  • Single posting newcomer
  • *
  • Posts: 7
Re: The 26 July 2006 build is out.
« Reply #17 on: July 27, 2006, 01:53:29 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]

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 »
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 :?

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5258
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.

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
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 »
chef de projet MASTER (AS400  RPGILE  C   and SYTEM)

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

Offline agent007se

  • Multiple posting newcomer
  • *
  • Posts: 25
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 »

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: [Select]
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  [email protected]
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  [email protected]
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  [email protected]
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: [Select]
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  [email protected]
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  [email protected]
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  [email protected]
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.


Offline agent007se

  • Multiple posting newcomer
  • *
  • Posts: 25
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)

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


Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5258
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 :-(

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!


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 »

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5258
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


Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5258
Re: The 26 July 2006 build is out.
« Reply #29 on: July 27, 2006, 05:35:29 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 ???