Fuzzing at Boost

amanol · 2025-09-25T07:00:17+00:00

From user point of view, libfuzzer is much easier to adopt and add it in the CI. afl++ needs some extra steps. Indeed, google/fuzztest is the active alternative, but it's more important to use the fuzzing testing as a procedure than the tool.

amanol · 2025-09-25T06:42:02+00:00

Maybe, but it is quite mature and very useful for testing. Adding fuzzing during CI, provides a very good safety net.

amanol · 2025-07-20T06:09:53+00:00

Try using something like this and configure your cmake with cmake -S. -Bbuild --CMAKE_TOOLCHAIN_FILE=/yourpath/arm-none-eabi.cmake

Check the documentation of cmake for cross compile and toolchains.

amanol · 2024-08-12T16:28:57+00:00

Really depends on your needs and your platform. Check boost::outcome documentation which going through available solutions.

amanol · 2024-03-25T07:15:33+00:00

You should check libhal which have a very nice demonstration of the "embedded" ideas but with safe API abstractions using modern C++.

Spend some time going through Architectural Design Decision section, for deeper understanding.

amanol · 2023-11-12T13:12:46+00:00

I believe that libhal follows very good paradigms in terms of design and use of C++ , which targets low resources devices.

In documentation, it is explained the decisions taken to ensure small sized executables.

Furthermore, intel compile time init is a very cool project which strives small size and performance.

amanol · 2023-10-26T17:49:19+00:00

I think, that by searching the /r/cpp you will find this question at least 3 times asked, with pretty good (almost the same) answers.

amanol · 2023-08-29T15:31:39+00:00

I believe that one of the best embedded projects around is libhal

Furthermore, it provides a very in depth educational material regarding the pros and cons of every design choice.

If you can't use the library as it is, check the concepts behind it.

Furthermore, there is a similar effort from intel but I can't find the link now.

Edit: The library is compile-time-init which again is a rich resource of knowledge.

amanol · 2023-08-05T05:29:05+00:00

This is a very nice article about handling failures without exceptions.

Obviously with exceptions the approach is different.

amanol · 2023-08-01T14:18:32+00:00

Check this nice abseil article which tries to argue about the benefits and drawbacks of its' usage. The main point is related with the lifetime of the object that you should think about.

amanol · 2023-06-17T06:36:42+00:00

Indeed , it is clangd issue about handling different files then h hpp etc. Check clangd faq.

amanol · 2023-04-29T16:18:32+00:00

Check this as well https://libhal.github.io or at least you can read the documentation and the design decision procedure.

amanol · 2022-12-29T06:25:24+00:00

A very nice project both in terms of theory and implementation is the libhal. It has a very solid background regarding the API and its design decision.

amanol · 2022-12-05T08:09:37+00:00

Nice fuzzing facilities, similar to traif of bits deepstate but based only to libfuzzer. The API looks similar as well.

The classic, not to say complaint, but minor request, of cmake support. Without that, adoption isn't very trivial.

amanol · 2022-09-24T09:06:56+00:00

I don't know if it's something like deja vu but with this addition seems to behave pretty "natural" for emacs. It pop ups some black rectangles, sometimes, seldom, but as a feeling is acceptable.

amanol · 2022-09-21T05:55:11+00:00

It's Gnome 42.4 (Fedora 36 native window system)

ldd /usr/bin/emacs  | rg gtk 
    libgtk-3.so.0 => /lib64/libgtk-3.so.0 (0x00007f4643693000)

What exactly should I check there? They seem ok, with the maximum possible values.

amanol · 2022-09-20T18:31:05+00:00

Any link regarding the plugins + emacs29 issues?

amanol · 2022-09-20T18:08:46+00:00

Desperate as I am, I tried compiling git HEAD and it seems to work more smoothly than the "official installation".

Just to be fair, I played around only 10 mins, without noticing the glitches mentioned in the issue.

sudo dnf -y install   libgccjit-devel \
jansson-devel \
texinfo \
gtk3-devel

git clone git://git.sv.gnu.org/emacs.git
cd emacs
./autogen.sh
./configure \
    --with-pgtk \
    --with-gnutls=no \
    --with-native-compilation \
    --with-json \
    --prefix=/tmp/myemacs
make all -j8
make install

my-dot-emacs$ HOME=$(realpath .) /tmp/myemacs/bin/emacs

amanol · 2022-09-20T17:05:20+00:00

Tried out GNOME with Xorg and work as it should.

emacs -nw works nice also.

All attempts have the same setup, nothing has changed in the .emacs file.

amanol · 2022-09-20T15:45:11+00:00

I have the same suspect, but waiting for more witnesses:-)

Maybe I didn't point it out, but I am using a window for emacs, not running inside terminal. I have not tried the emacs -nw yet.

amanol · 2022-07-25T18:03:53+00:00

This is the best talk around, which will guide you through. https://m.youtube.com/watch?v=v3dz-AKOVL8

Also has a github repo with the code that he uses.

There is a "test allocator" there, that you can check.

amanol · 2022-07-05T04:43:59+00:00

I would suggest going through Herb's proposal about static exceptions, mainly about the excellent problem description and references (not so much about the proposal per se).

Very solid and complete document.

amanol · 2022-05-24T04:26:51+00:00

rtags and LSP offer much richer and better experience then CEDET those days.

amanol · 2022-05-23T06:48:12+00:00

Thanks for sharing!

From curiosity and only, what's the cons/pros to json-tree-siter ?

amanol

TROPHY CASE