Bad executable

[gmail Vladimir Koković]

More details about the NetBeans project:

Main folder

-----------

/asoft-src/ispp-64/linux/vk-trace:
total 48
drwxr-xr-x 6 root root 4096 јун 24 08:38 .
drwxr-xr-x 9 root root 4096 јун 24 08:30 ..
drwxr-xr-x 3 root root 4096 јун 24 06:14 build
drwxr-xr-x 2 root root 4096 јун 24 06:17 CVS
-rw-r--r-- 1 root root   11 јун 23 06:52 .cvsignore
-rw-r--r-- 1 root root  163 јун 24 06:14 .dep.inc
drwxr-xr-x 3 root root 4096 јун 23 06:55 dist
-rw-r--r-- 1 root root 1635 јун 24 05:56 main.c
-rw-r--r-- 1 root root 3482 јун 23 06:52 Makefile
-rw-r--r-- 1 root root 1588 јун 23 18:53 mira.c
drwxr-xr-x 4 root root 4096 јун 24 00:04 nbproject
-rw-r--r-- 1 root root  851 јун 23 06:55 vk-trace-unix.c


Build folder

------------

/asoft-src/ispp-64/linux/vk-trace/build/Debug/GNU-Linux/_ext/5fd253b2:
total 712
drwxr-xr-x 2 root root   4096 јун 24 06:14 .
drwxr-xr-x 3 root root   4096 јун 24 06:14 ..
-rw-r--r-- 1 root root 131032 јун 24 06:14 main.i
-rw-r--r-- 1 root root 101712 јун 24 06:14 main.o
-rw-r--r-- 1 root root     88 јун 24 06:14 main.o.d
-rw-r--r-- 1 root root 247515 јун 24 06:14 main.s
-rw-r--r-- 1 root root  70809 јун 24 06:14 vk-trace-unix.i
-rw-r--r-- 1 root root  46808 јун 24 06:14 vk-trace-unix.o
-rw-r--r-- 1 root root    106 јун 24 06:14 vk-trace-unix.o.d
-rw-r--r-- 1 root root 105004 јун 24 06:14 vk-trace-unix.s


Dist folder

-----------

/asoft-src/ispp-64/linux/vk-trace/dist/Debug/GNU-Linux:
total 96
drwxr-xr-x 2 root root  4096 јун 24 06:14 .
drwxr-xr-x 3 root root  4096 јун 23 06:55 ..
-rwxr-xr-x 1 root root 89472 јун 24 06:14 vk-trace

On 24.6.21. 11:06, Jonathan Wakely wrote:
> On Thu, 24 Jun 2021 at 07:34, gmail Vladimir Koković via Gcc-help
> <gcc-help@gcc.gnu.org> wrote:
>>
>> I'm not sure if this is a GCC bug so I'm looking for help.
>>
>> Namely, although everything is regular when it comes to .C programs, the
>> result is defective executable.
> Defective how? You haven't even told us what the error is.
>
> As it says at https://gcc.gnu.org/bugs/
>
> "Before reporting that GCC compiles your code incorrectly, compile it
> with gcc -Wall -Wextra and see whether this shows anything wrong with
> your code. Similarly, if compiling with -fno-strict-aliasing -fwrapv
> -fno-aggressive-loop-optimizations makes a difference, or if compiling
> with -fsanitize=undefined produces any run-time errors, then your code
> is probably not correct. "
>
> Have you tried those options?