How to troubleshoot memory issues, such as segmentation faults in francinette-image

[kugorang]

Hi, the previously reported segmentation fault that occurs when running libft-war-machine on francinette-image has reoccurred. I have tried the workaround you suggested last time, but it is not working.

Also, I'm currently working on the ft_printf assignment and the memory-related logic doesn't seem to be working properly there either (it behaves differently on macOS).

To resolve these issues, could you please walk me through the latest version of the workaround as easily and in as much detail as possible?

[WaRtr0]

Hi @kugorang ,

You're right, the segmentation fault issue was only resolved for the libft tests using war-machine. The main problem was related to the use of fsanitize, which seems to have issues in Docker environments due to insufficient permissions to communicate with the host API. This results in segmentation faults.

The best solution here is to remove fsanitize entirely and either replace it with valgrind or run the tests without any sanitizers.

Regarding your ft_printf issue, I would recommend testing each framework separately rather than running everything through Francinette. Some testers seem to have inconsistencies...

[kugorang]

Hi, first of all, thank you for your response.

It sounds like the big issue is that your tester, which is targeted for macOS, is not compatible with linux. For example, there are cases where a tester that doesn't work with francinette-image works with [linux-francinette](https://github.com/gemartin99/francinette). This repository is supposedly ported for the linux operating system, which is why some testers work.

As you said, I'll try to use each tester instead of francinette-image, thanks for checking :)

[kugorang]

Hi, I just came across a repository that complements yours and seems to have fixed the segmentation fault in libft.

https://github.com/SMOSTAFAH1/francinette-installer/blob/master/f.sh

For ft_printf, fsoares still doesn't work properly, but I thought it might give you some clues, and I'll comment further.

[WaRtr0]

The repository (francinette-installer) doesn't actually fix anything; it simply installs the original Francinette.

The francinette-image was created as a wrapper inside a Docker container for 42 sessions where users don’t have sufficient permissions to install it directly. If the repository works for you, it just means you’ve never actually needed to use mine! 😄