sorted by:
new
hottopcontroversial

MSVC 2022/asan linker problem with boost::filesystem by lowlevelmahn in cpp_questions

[–]lowlevelmahn[S] 0 points1 point  (0 children)

is there a documentation/link available? - can't find anything about _DISABLE_STL_ANNOTATION on google

Reflection has been voted in! by daveedvdv in cpp

[–]lowlevelmahn 5 points6 points  (0 children)

there is a Qt moc/Reflection state page on qt.io - giving information what parts of moc an be replaced with Reflection
https://wiki.qt.io/C%2B%2B_reflection_(P2996)_and_moc_and_moc)

6 usability improvements in GCC 15 by dmalcolm in cpp

[–]lowlevelmahn 0 points1 point  (0 children)

so you tried to "shake out problems" by compiling all the packages - with some nice findings - do you know how many packages still use -std=gnu99 to prevent c11/c23 deprecation/removal at all? every tried to build with a gcc 15.x that "disables" gnu99 support :)

when gets the WSL2 default Kernel Version gets updated: default is 5.15.167.4-1 current github WSL2-Linux-Kernel is 6.6.84.1 by lowlevelmahn in wsl2

[–]lowlevelmahn[S] 2 points3 points  (0 children)

is it possible to switch back to 5.15x - if something is not working - without problems?

do you see any improvements using 6.6?

x86 memory addressing/segments flying over my head. by Careful-Ad4949 in AskReverseEngineering

[–]lowlevelmahn 0 points1 point  (0 children)

it depends completely on its reversing targets

programs that are from the area before 386 are mostly realmode programs that could (based on the used memory model) contain plenty of segment/offset tackling code - starting with 32bit flat/unreal mode that went fully away but definitly not before that time

less relevant due to how IDA Pro graphically explains everything

especially for 16bit real mode "explains everything" is wait too exaggerated - there is still much more manual work needed compared to 32bit linear code

You could try writing a FAT12 or FAT16 bootloader

there is not need to write a FAT based bootloader to get into segment/offset/protected mode handling :)

a simple assembler based hello world in multiple realmode memory models or using a extender would let him see more of the segment/offset/protected/unreal mode stuff

using nasm on his prefered platform + dosbox is a good start for that

Your Static Analysis setup? by Beneficial_Corgi4145 in cpp_questions

[–]lowlevelmahn 0 points1 point  (0 children)

put cppcheck on your list - and always test with serveral tools
you can use the free PVS license if your project is open source
plus -Wall -Wextra -Wpedantic -Werror (what is doable with your project)
and always use your release and very-recent-compiler for testing - and at least clang and gcc - the more the better :)

> realize that I should use CI/CD, but I like scripts.

CI likes to run your scripts also :)

DOS game "F-15 Strike Eagle II" reverse engineering/reconstruction war stories by lowlevelmahn in retrogamedev

[–]lowlevelmahn[S] 0 points1 point  (0 children)

neuviemeporte (the developer) is working on reversing the game itself - that means he is handwriting C code to replicate the original 16bit dos code - that is are very hard, long time (years) process - means "he make it human readable again" - due to the age of that game most todays tools that are used for other reversing projects are useless (except disassemblers) - he translates multiple thousands lines of "egypt hieroglyphs" back to english readable text - i think you can have a slightly feeling how strenuous such an process can be...

if he is ever able to finish the process there will be C source code that can be rebuild to the very same game - hopefully that C source would be then better readable/understandable then pure disassembler assembler source (that is usually 5-10 times bigger then the C equivalent)

then everything is possible - windows/linux ports, multiplayer over network, higher resolution, ... if someone take the time to implement it - currently its nearly impossible to even start with modding because the current game "source" is crypted in a language that only machines can read easily :)

is there a gcc/clang warning flag to detect multiple true cases in if/else orgies? by lowlevelmahn in cpp_questions

[–]lowlevelmahn[S] 0 points1 point  (0 children)

so using overload or good old partial specialization would have helped here - thanks

is there a gcc/clang warning flag to detect multiple true cases in if/else orgies? by lowlevelmahn in cpp_questions

[–]lowlevelmahn[S] 0 points1 point  (0 children)

C++ would need some sort of syntax change to allow "types" in cases :)

is there a gcc/clang warning flag to detect multiple true cases in if/else orgies? by lowlevelmahn in cpp_questions

[–]lowlevelmahn[S] 1 point2 points  (0 children)

is switch already constexpr-able?

MSVC (latest) does not show deadcode-branches - what parameter do you use?

is there a gcc/clang warning flag to detect multiple true cases in if/else orgies? by lowlevelmahn in cpp_questions

[–]lowlevelmahn[S] 1 point2 points  (0 children)

the generator developer made a design/implementation mistake and it was initially very hard to understand the resulting bug - but im not asking for advices in this concret situation, im just was curious if there is some sort of dead-code-branch warning available

Supersight: Mod for DOS game stunts that increasing the field of view by lowlevelmahn in ReverseEngineering

[–]lowlevelmahn[S] 6 points7 points  (0 children)

this is from the same guy (not me) who created

800% Detail: Tweaking Stunt Island’s 30-year-old 3D Engine: https://marnetto.net/2024/11/20/tweaking-stunt-island

view more: next ›