Recent Posts

Pages: 1 2 [3] 4 5 6 7 8 ... 10
21
Nightly builds / Re: The 13 December 2020 build (12240) is out.
« Last post by eckard_klotz on January 17, 2021, 10:43:29 am »
Hello oBFusCATed.

Thanks for your reply and please accept my apologize for my late answer.

First of all thanks for your tip where to find the "Clear changes history" item.

Quote
No, it is not a known problem.

Quote
Also first make sure that geany/scite/codelite/notepad++ behave differently.
  • I'm unsure what you mean with mentioning the behaviour of other tools.
  • As far as I understand it it is a problem located in a third-party library used with Code::Blocks.
  • So I understand, that it has to be solved by the third party project.
  • Never the less it is a already known problem. Otherwise you would not mention the other tools.
  • Or do you expect that I as user of Code::Blocks set up a bug-report in the third-party project with the statement, that the third-party library results in a problem with Code::Blocks?

Quote
Give link or post a ticket on sf.net with exact steps to reproduce the problem.
  • I think this is the key-question.
  • I completely understand, that with out an reproduce able example it will be not possible to search for the reason.
  • And yes you are right, the examples in the discussion mentioned above are working with C/Cpp and H files.
  • However, over the time and randomly I still face the issue with C/Cpp and H files.
  • Thus the problem is definitely not solved.
  • What I can tell you is, that it happens if you edit several files in parallel.
    • Yesterday I made first some in a header-file in different lines. 
    • Than I modified some other files (cpp). 
    • And when I than turned back to the header to undo the last modification of one line, the editor removed the change in an additional line also.
  • It seams that the Undo memory will be corrupted over the time or the module is compressing the oldest modifications to one.
  • Unfortunately I was not able to reproduce this effect to provide it as an reproduce able example.

But my main request was how to clear the undo-history and this question was answered by you. So once again thanks for your support.

Stay well and healthy,
                                Eckard Klotz.
22
Development / Re: addr2lineui assertion triggered with wxwidgets 3.14
« Last post by Miguel Gimenez on January 16, 2021, 07:34:02 pm »
Thanks for testing. I have created a ticket with the patch:

https://sourceforge.net/p/codeblocks/tickets/1059/
23
Using Code::Blocks / Re: Win32 Debug/Release
« Last post by sevendogzero on January 16, 2021, 07:26:00 pm »
Hammering out some MessageCrackers now. Good to be back
24
Using Code::Blocks / Re: Win32 Debug/Release
« Last post by sevendogzero on January 16, 2021, 07:07:29 pm »
Tried that.
Back in the Borland C++ 5 days, I recalled having to clear those Bin folders, so I tried it...and presto!

I'm also thinking Precompiled headers seemed to snag me back then. For now, the step by step
code proofing refreshed my memory on Windows programming.
On to the next problem.
25
Development / Re: addr2lineui assertion triggered with wxwidgets 3.14
« Last post by reckless on January 16, 2021, 01:26:24 pm »
that seems to have done the trick :D thank you.
Ill see if anything else out of the ordinary crops up, but so far no problems.
26
Using Code::Blocks / Re: Win32 Debug/Release
« Last post by stahta01 on January 16, 2021, 07:59:39 am »
Read and re-read my project code..tightened up everything, every warning..still did not execute messages in WndProc while a Release target.

Solution:
1. Deleted all files in Bin\Release
2. Delete both manifest files (one in the root of my project, one in the Bin/Release folder)

It works now. Maybe this will make sense to someone. Just happy to go to the next step.

Before doing all that next time; try rebuilding the project instead of just building the project.

Tim S.
27
Using Code::Blocks / Re: Win32 Debug/Release
« Last post by sevendogzero on January 16, 2021, 07:18:57 am »
Read and re-read my project code..tightened up everything, every warning..still did not execute messages in WndProc while a Release target.

Solution:
1. Deleted all files in Bin\Release
2. Delete both manifest files (one in the root of my project, one in the Bin/Release folder)

It works now. Maybe this will make sense to someone. Just happy to go to the next step.

28
Help / Re: How to convert Makefile to Code::Blocks project
« Last post by oBFusCATed on January 15, 2021, 09:53:45 pm »
3. Project -> Build options -> Linker settings -> Linker executable -> Auto detect.

For the debugger. Please post the full debugger log. Are you able to run your project? Are the executable and work dir paths setup correctly in Project -> Properties?
29
Using Code::Blocks / Re: [SOLVED] How to suppress a specific warning ?
« Last post by stahta01 on January 15, 2021, 09:31:14 pm »
FYI: Option "-w" stops all warnings and should never be used by a newbie programmer!!!!

Tim S.
30
Help / Re: How to convert Makefile to Code::Blocks project
« Last post by umen on January 15, 2021, 09:25:58 pm »
1 . Thanks, i found the answer here : and it compiles great  ( replace all with debug in the make file .. )
https://stackoverflow.com/questions/28542408/how-use-a-makefile-with-codeblocks

but when i try to debug it I'm getting (added -g)
Code: [Select]
gcc  -g -fno-stack-protector -static -O2 test.c test1.S -o test.elf
Active debugger config: GDB/CDB debugger:Default
Building to ensure sources are up-to-date
Selecting target:
Debug
Adding source dir: /home/vagrant/example/
Adding source dir: /home/vagrant/example/
Adding file: /home/vagrant/example/bin/Debug/example
Changing directory to: /home/vagrant/example/.
Set variable: LD_LIBRARY_PATH=.:
Starting debugger: /usr/bin/gdb -nx -fullname -quiet  -args /home/vagrant/example/bin/Debug/example
Setting SHELL to '/bin/sh'
done
Setting breakpoints
Debugger name and version: GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Starting the debuggee failed: No executable file specified.
Debugger finished with status 0



3 . yes I'm using 20.3 , what fix you talking about ?
Pages: 1 2 [3] 4 5 6 7 8 ... 10