[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tinycc-devel] execve being called with wrong path
From: |
Brian Mayer |
Subject: |
Re: [Tinycc-devel] execve being called with wrong path |
Date: |
Mon, 7 Oct 2024 14:46:02 -0300 |
Hi Ekaitz, thanks for the help, here is the output you asked for:
# strace ./a.out > log 2>&1
The contents of log:
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
execve("./a.out", 0x5c8c977f9420, 0x7ffe36345d40) = 0
[stopped 1407 (5)]
arch_prctl(4098, 0x7900c5835b68) = 0
set_tid_address(0x7900c5835fd0) = 45214
brk(NULL) = 0x3ce78000
brk(0x3ce7a000) = 0x3ce7a000
mmap(0x3ce78000, 4096, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_FIXED,
-1, 0) = 0x3ce78000
[stopped 2943 (b)]
[stopped 2943 (b)]
[stopped 2943 (b)]
...
The last line keeps going, it only stopped because I interrupted the process.
Good to see that it was called with the right path. But I still do not
know why is this seg faulting.
- [Tinycc-devel] execve being called with wrong path, Brian Mayer, 2024/10/07
- Re: [Tinycc-devel] execve being called with wrong path, Ekaitz Zarraga, 2024/10/07
- Re: [Tinycc-devel] execve being called with wrong path,
Brian Mayer <=
- Re: [Tinycc-devel] execve being called with wrong path, Ekaitz Zarraga, 2024/10/07
- Re: [Tinycc-devel] execve being called with wrong path, Brian Mayer, 2024/10/07
- Re: [Tinycc-devel] execve being called with wrong path, Yao Zi, 2024/10/09
- Re: [Tinycc-devel] execve being called with wrong path, Yao Zi, 2024/10/09
- Re: [Tinycc-devel] execve being called with wrong path, Brian Mayer, 2024/10/09