Questions about Segmentation Fault Errors in libft-war-machine

[kugorang]

Hello, I'm hyeonwki, studying at 42 Gyeongsan Campus. First of all, thank you for making francinette available on the 42 cluster. I'm writing to the Discussion because unlike the current francinette, libft-war-machine doesn't seem to work properly when using francinette-image.

Typically, I get a Segmentation Fault error in the ft_isalpha and ft_isdigit functions, and the error log is shown below. The Your result actually shows a blank line.

Errors in isalpha: /francinette/temp/libft/war-machine/tests/Part1_functions/ft_isalpha
Test 2:
    i = '0';
    while (i <= '9')
    { }
        ft_print_result(ft_isalpha(i));
        i++;
    }
Expected (cat -e test02.output):
0000000000
Your result (cat -e user_output_test02):

Errors in isdigit: /francinette/temp/libft/war-machine/tests/Part1_functions/ft_isdigit
Test 2:
    i = '0';
    while (i <= '9')
    { }
        ft_print_result(ft_isdigit(i));
        i++;
    }
Expected (cat -e test02.output):
1111111111
Your result (cat -e user_output_test02):

Now, when I run plain francinette on the latest version of MacOS on my 2019 Intel MacBook Pro, this part runs fine. Is there any reason why only the libft-war-machine test is having problems, and I would like to know the reason for this, and how I can debug it in the future if this happens again. If you can debug yourself by checking the logs located in the path /francinette/temp/libft/war-machine/deepthought, I would appreciate it if you could tell me how to access this path from the docker that francinette-image creates.

[WaRtr0]

Hello hyeonwki,
Thank you for reporting this issue. Indeed, several users have reported similar problems with libft-war-machine when using francinette-image outside of 42 school computers.
After investigation, it appears to be a privilege issue between Docker and AddressSanitizer (ASan), where ASan doesn't have proper access to ptrace, causing random segmentation faults.

I will implement a mount point for the temp directory in ~/francinette-image/temp/ to facilitate debugging.
Could you please provide:

The OS and version running on the Gyeongsan campus computers
The output of uname -a if possible

This information would be very helpful as I haven't encountered these privilege issues at 42 Lyon campus, and understanding the differences between campuses will help me provide better support.

Note

If anyone from other 42 campuses is following this discussion, please feel free to share your campus's OS & version. This will help me ensure francinette-image works reliably across all 42 schools.

But adding a fix is challenging since I don't have direct access to the war-machine repository, and it seems to work on some campuses... Quite ironic given that Docker's purpose is to prevent these kinds of issues, but in this case, it's actually causing them! 😄

[WaRtr0]

I'm not on my PC right now, but this error is quite specific, and I couldn’t manage to reproduce it. In the meantime, I’ve fixed a lot of other errors, but this seems to be something else entirely.

Redo an install of the fix_war_machine branch, and if it still doesn't work

Run :

chmod -R 777 francinette-image

Then close and reopen your terminal.

If that doesn’t work, you might want to edit your .zshrc file in your home directory and remove the following from the docker start command:

-v /.../francinette-image/temp:/francinette/temp
-v /.../francinette-image/logs/:/francinette/logs

Make sure to leave the other parts of the command intact. After making these changes, close and reopen your terminal. If you’re using the terminal in VSCode, try closing and reopening VSCode entirely.

[kugorang]

I'm not on my PC right now, but this error is quite specific, and I couldn’t manage to reproduce it. In the meantime, I’ve fixed a lot of other errors, but this seems to be something else entirely.

Redo an install of the fix_war_machine branch, and if it still doesn't work

Run :

chmod -R 777 francinette-image

Then close and reopen your terminal.

If that doesn’t work, you might want to edit your .zshrc file in your home directory and remove the following from the docker start command:

-v /.../francinette-image/temp:/francinette/temp -v /.../francinette-image/logs/:/francinette/logs

Make sure to leave the other parts of the command intact. After making these changes, close and reopen your terminal. If you’re using the terminal in VSCode, try closing and reopening VSCode entirely.

Hi, I ran all the commands you gave me, but it didn't work.

Even when I ran the last command, I still get permission denied for /francinette-image.

The log below is the error message in the terminal after performing all the actions.

Error response from daemon: error while creating mount source path '/francinette-image/temp': mkdir /francinette-image: permission denied
Error: failed to start containers: run-paco

[WaRtr0]

Hi,
This shouldn't be happening anymore since you've removed the -v /.../francinette-image/temp:/francinette/temp -v /.../francinette-image/logs/:/francinette/logs from your .zshrc

• most importantly, don't reinstall, just restart your terminal.

Could you share the content of your files:

cat ~/.zshrc

and

cat ~/.bashrc

[WaRtr0]

I finally found the problem!!!

Do an uninstall with:

bash -c "$(curl -fsSL https://raw.githubusercontent.com/WaRtr0/francinette-image/fix_war_machine/uninstall.sh)"

and then install:

bash -c "$(curl -fsSL https://raw.githubusercontent.com/WaRtr0/francinette-image/fix_war_machine/install.sh)"

[kugorang]

I'm really sorry, but my francinette-image still doesn't work. It says the installation is complete, but I keep running into the temp permissions issue.

Error response from daemon: error while creating mount source path '/francinette-image/temp': mkdir /francinette-image: permission denied
Error: failed to start containers: run-paco

Currently, .bashrc is a non-existent file and .zshrc looks like this

# Set up the prompt

autoload -Uz promptinit
promptinit
prompt adam1

setopt histignorealldups sharehistory

# Use emacs keybindings even if our EDITOR is set to vi
bindkey -e

# Keep 1000 lines of history within the shell and save it to ~/.zsh_history:
HISTSIZE=1000
SAVEHIST=1000
HISTFILE=~/.zsh_history

# Use modern completion system
autoload -Uz compinit
compinit

zstyle ':completion:*' auto-description 'specify: %d'
zstyle ':completion:*' completer _expand _complete _correct _approximate
zstyle ':completion:*' format 'Completing %d'
zstyle ':completion:*' group-name ''
zstyle ':completion:*' menu select=2
eval "$(dircolors -b)"
zstyle ':completion:*:default' list-colors ${(s.:.)LS_COLORS}
zstyle ':completion:*' list-colors ''
zstyle ':completion:*' list-prompt %SAt %p: Hit TAB for more, or the character to insert%s
zstyle ':completion:*' matcher-list '' 'm:{a-z}={A-Z}' 'm:{a-zA-Z}={A-Za-z}' 'r:|[._-]=* r:|=* l:|=*'
zstyle ':completion:*' menu select=long
zstyle ':completion:*' select-prompt %SScrolling active: current selection at %p%s
zstyle ':completion:*' use-compctl false
zstyle ':completion:*' verbose true

zstyle ':completion:*:*:kill:*:processes' list-colors '=(#b) #([0-9]#)*=0=01;31'
zstyle ':completion:*:kill:*' command 'ps -u $USER -o pid,%cpu,tty,cputime,cmd'

if ! systemctl status docker | grep running &> /dev/null; then
		echo "[Francinette] Starting Docker..."
		sleep 1
		exec "/bin/zsh"
fi
if ! docker image ls | grep francinette-image &> /dev/null; then
	if docker image ls 2>&1 | grep permission &> /dev/null; then
		echo "[Francinette] Permission Error"
	else
		if ! [ -f /home/hyeonwki/francinette-image/francinette.tar ] || docker load < /home/hyeonwki/francinette-image/francinette.tar 2>&1 | grep "no such file"  &> /dev/null; then
			echo "[Francinette] Error width file "francinette.tar""
			docker build -t francinette-image /home/hyeonwki/francinette-image
			docker image save francinette-image > /home/hyeonwki/francinette-image/francinette.tar
		else
			echo "[Francinette] Loading the docker container"
			docker load < /home/hyeonwki/francinette-image/francinette.tar
		fi
		exec "/bin/zsh"
	fi
fi
if ! docker ps | grep "francinette-image" &> /dev/null; then
	if docker run -d -i -v /home:/home -v /goinfre:/goinfre -v /sgoinfre:/sgoinfre --name run-paco francinette-image /bin/bash 2>&1 | grep "already" &> /dev/null; then
		docker start run-paco
	fi
fi
alias francinette=/home/hyeonwki/francinette-image/run.sh

alias paco=/home/hyeonwki/francinette-image/run.sh

[kugorang]

Hi, I've forked this repository to roll back the code you recently worked on and set the URL to point to this forked repository.

However, I'm still getting the error below.

Error response from daemon: error while creating mount source path '/francinette-image/temp': mkdir /francinette-image: permission denied
Error: failed to start containers: run-paco

Maybe there is a path to the image managed in docker.io somewhere? I'd like to use francinette-image as a rolled back version from before the first operation, but it's frustrating that even this doesn't work. Please let me know how I can fix this and we can move forward, thanks.

[WaRtr0]

Maybe an old container of the image (with cached mount points) is just stopped and every time you open your terminal, it tries to restart it but fails with mount point errors...
I had you uninstall/remove all of this.

Run this - it's a bit brutal but it will completely reset everything Docker-related:

bash -c "$(curl -fsSL https://raw.githubusercontent.com/WaRtr0/francinette-image/fix_war_machine/uninstall.sh)"

and

docker stop $(docker ps -a -q)
docker rm $(docker ps -a -q)
docker rmi $(docker images -a -q) -f
docker system prune -a -f --volumes

Then install francinette :

bash -c "$(curl -fsSL https://raw.githubusercontent.com/WaRtr0/francinette-image/fix_war_machine/install.sh)"

[kugorang]

Maybe an old container of the image (with cached mount points) is just stopped and every time you open your terminal, it tries to restart it but fails with mount point errors... I had you uninstall/remove all of this.

Run this - it's a bit brutal but it will completely reset everything Docker-related:

bash -c "$(curl -fsSL https://raw.githubusercontent.com/WaRtr0/francinette-image/fix_war_machine/uninstall.sh)"

and

docker stop $(docker ps -a -q)
docker rm $(docker ps -a -q)
docker rmi $(docker images -a -q) -f
docker system prune -a -f --volumes

Then install francinette :

bash -c "$(curl -fsSL https://raw.githubusercontent.com/WaRtr0/francinette-image/fix_war_machine/install.sh)"

Hi, I finally got this resolved, when I typed in the docker command and ran the install.sh command, install.sh took longer than before and it felt like it was really installing.

The peculiarity is that after the uninstall, the path is set to .(dot?) instead of ~(home) - I've noticed this before, and it was the same this time, but I worked around it by moving to ~(home) after the uninstall.

Finally, the Segmentation Fault issues that were bugging me are also gone, for which I am eternally grateful. I'm wondering if the tests that were previously problematic and the new logs you added are still problematic and hard for me to see.

[WaRtr0]

That's great! I'm really glad it finally works. Regarding the.(dot?) instead of ~(home) , it's strange because for the git clone, I specifically set $HOME/francinette-image, but as long as it works... Temporary files and logs should normally be available in $HOME/francinette-image, though I can't guarantee they'll be easy to read.

[kugorang]

Okay, we've read everything you've written. The last thing I'd like to ask is, is there anything I can do to contribute to this repo?

I'm a cadet who started the 42 course in October this year, and now that francinette has been publicly archived, I'm hoping that this repo will continue to be maintained and eventually become a helper for as many assignments as possible.

[WaRtr0]

Thank you for your interest in contributing! While I'm not very available at the moment. I'm planning to develop a new testing framework that would make it easier for people to contribute tests for 42 projects while maintaining a standardized format/norm. This would help avoid compatibility issues while remaining scalable.

The key features I'm envisioning:

• Easy to use in vanilla form on 42 school computers without requiring Docker
• Docker support included as a backup wrapper
• Standardized format for contributions
• Built with scalability in mind

I remain open to any contributions or ideas francinette-image and my upcoming testing framework. I expect to start working on this new project approximately mid-January.

If you're interested in contributing, feel free to keep an eye on the repository or share any ideas you may have.