Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
Patches welcome? Defaults are debatable I don't intend to debate them, but I don't intend to change it at the moment.
2
as for justification in general, try this https://quuxplusone.github.io/blog/2018/12/06/dont-use-weverything/

Use of -Weverything is based on a misconception about what it is for.  It gives you every warning possible regardless of any other flags, whether it's appropriate to your context or not. Its only known usage is for the development of clang, not development using clang.  Therefore, its use by sorcerer's apprentices is highly discouraged.

I'm willing to become a code contributor if that's what it takes to change this to -Wall.

-pat


3
Development / Re: RFC: Backticks
« Last post by oBFusCATed on Today at 03:12:10 pm »
quotes=="
backticks==`

 ::)
4
Development / Re: RFC: Backticks
« Last post by ollydbg on Today at 02:04:23 pm »
What happens without the quotes?
Generally backticks are more useful in the compiler or linker options and not for search paths.

If I remove the backtick, then the build log becomes:

Code
g++.exe -Wall -fexceptions -g -I"echo aaa" -c D:\code\test_git_temp\test_cmdcmd\main.cpp -o obj\Debug\main.o
5
Development / Re: RFC: Backticks
« Last post by oBFusCATed on Today at 01:58:56 pm »
What happens without the quotes?
Generally backticks are more useful in the compiler or linker options and not for search paths.
6
Development / Re: RFC: Backticks
« Last post by ollydbg on Today at 01:54:43 pm »
I can build this branch under Windows.

But I don't know how to test it.

I can write some code in the compiler include search path, such as:

Code
`echo aaa`

Then, I got such build command line:

Code
g++.exe -Wall -fexceptions -g -I"`echo aaa`" -c D:\code\test_git_temp\test_cmdcmd\main.cpp -o obj\Debug\main.o

It looks like the backtick not get executed?
7
Using Code::Blocks / Re: Problem with svn 12446
« Last post by oBFusCATed on Today at 01:33:00 pm »
I can reproduce this with gcc 11.1, but I'm not sure it is the compiler. Somehow the data items gets corrupted when they get to the sort function. Investigating.
8
Hi, thanks for the response!

ollydbg. Thanks for the Page and info as I was able to get the wxwidget pretty printing to work with the help form the page. I fell into a few minor holes, which could filed in by updating the page so other people do not fall into the same holes, which are/were:
1) In the Menu->Settings->Debugger settings. Open the debugger plugin setting dialog and uncheck the "Disable startup scripts (-nx) (GDB only)" option.

I think this option should be "checked on", I mean we don't need the startup scripts.


Quote
2) If you are using the https://github.com/wxWidgets/wxWidgets/blob/master/misc/gdb/print.py file then add the following to the gdbinit file:
sys.path.insert(0, 'D:/temp')         
from wxprint import register_wxwidgets_printers
register_wxwidgets_printers (None)

Rember to change the directory to where you have saved the print.py file.
I don't do like that, I just shows what I did in this post:
Re: Debugger: use gdb python pretty printer for the libstdcxx under msys2
You don't need the "hard-coded path" in those settings.


Quote
3) Update it to change the "source F:\msys64\mingw64\etc\gdbinit" to "source $(TARGET_COMPILER_DIR)etc\gdbinit"
This is correct, I also do like this.


Quote
4) You may want to change the note about the "register_libstdcxx_printers(None)" additional line was added to MSYS in https://github.com/msys2/MINGW-packages/pull/6351 (6-Apr-2020) and if people are using a later version then they do not need to do anything.
Yes, I think msys2 already has configured the pretty printer for the libstdcxx library, what we need is to add some codes to the "gdbinit" file which support the wx's pretty printer.
10
Help / Re: Project - compiler changes do not cause debugger to change
« Last post by oBFusCATed on Today at 11:06:13 am »
Works fine for me at least on linux with the CB project.
I have two compilers which have different debugger's configurations selected (settings -> compiler -> [my compiler] -> toolchain executables -> debugger) and if I switch and then use debug -> start it print the correct configuration in the log.

What are the exact steps to reproduce this problem?
Pages: [1] 2 3 4 5 6 ... 10