Gcc make fatal errors encountered - cannot

gcc make fatal errors encountered - cannot

@beyou923 I tried for gcc-7.5.0 and it worked. The problems seems that something wrong about your gcc configure../configure --enable-languages. I have also found that the cc compiler with Solaris hasn't always compiled what i wanted to.. So what i would suggest you do is download gcc from say www. I found the problem reported here: arm-xilinx-eabi-gcc.exe: fatal error: no input files make[3]: *** [Makefile:18: libs] Error 1.

watch the video


Gcc make fatal errors encountered - cannot - confirm. agree

'=' <-- `=' +-------+ SA_SIGINFO SIGPIPE: [libjvm.so+0xb60080], sa_mask[0]=11111111011111111101111111111110, sa_flags=SA_RESTART +--------------------------------------------------------------------------------------- pointer +---------------------------------------------------------------------------------------------- "=>" current thread

This includes all Java threads and some VM internal threads, but does not include any native threads created by the user application that have not attached to the VM, as shown in the following example.

Java Threads: ( => current thread ) 0x00007f102c469800 JavaThread "C2 CompilerThread0" daemon [_thread_blocked, id=18302, stack(0x00007f0f16f31000,0x00007f0f17032000)] 0x00007f102c468000 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=18301, stack(0x00007f0f17032000,0x00007f0f17133000)] 0x00007f102c450800 JavaThread "Finalizer" daemon [_thread_blocked, id=18298, stack(0x00007f0f173fc000,0x00007f0f174fd000)] 0x00007f102c448800 JavaThread "Reference Handler" daemon [_thread_blocked, id=18297, stack(0x00007f0f174fd000,0x00007f0f175fe000)] =>0x00007f102c013000 JavaThread "main" [_thread_in_native, id=18245, stack(0x00007f10345c0000,0x00007f10346c0000)] Other Threads: 0x00007f102c43f000 VMThread "VM Thread" [stack: 0x00007f0f175ff000,0x00007f0f176ff000] [id=18296] 0x00007f102c54b000 WatcherThread [stack: 0x00007f0f15bfb000,0x00007f0f15cfb000] [id=18338]

The thread type and thread state are described in Thread Section Format.

VM State

The next information is the VM state, which indicates the overall state of the virtual machine. Table A-3 describes the general states.

Table A-3 VM States

General VM StateDescription

Normal execution.

All threads are blocked in the VM waiting for a special VM operation to complete.

A special VM operation is required, and the VM is waiting for all threads in the VM to block.

The VM state output is a single line in the error log, as follows:

VM state:not at safepoint (normal execution)

Mutexes and Monitors

The next information in the error log is a list of mutexes and monitors that are currently owned by a thread, as shown in the following example. These mutexes are VM internal locks rather than monitors associated with Java objects. The following is an example to show how the output might look when a crash happens when VM locks are held. For each lock, the log contains the name of the lock, its owner, and the addresses of a VM internal mutex structure and its OS lock. In general, this information is useful only to those who are very familiar with the HotSpot VM. The owner thread can be cross-referenced to the thread list.

VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])[0x007357b0/0x0000031c] Threads_lock - owner thread: 0x00996318 [0x00735978/0x000002e0] Heap_lock - owner thread: 0x00736218

Heap Summary

The next information is a summary of the heap, as shown in the following example. The output depends on the garbage collection (GC) configuration. In this example, the serial collector is used, class data sharing is disabled, and the tenured generation is empty. This probably indicates that the fatal error occurred early or during startup, and a GC has not yet promoted any objects into the tenured generation.

Heap def new generation total 576K, used 161K [0x46570000, 0x46610000, 0x46a50000) eden space 512K, 31% used [0x46570000, 0x46598768, 0x465f0000) from space 64K, 0% used [0x465f0000, 0x465f0000, 0x46600000) to space 64K, 0% used [0x46600000, 0x46600000, 0x46610000) tenured generation total 1408K, used 0K [0x46a50000, 0x46bb0000, 0x4a570000) the space 1408K, 0% used [0x46a50000, 0x46a50000, 0x46a50200, 0x46bb0000) compacting perm gen total 8192K, used 1319K [0x4a570000, 0x4ad70000, 0x4e570000) the space 8192K, 16% used [0x4a570000, 0x4a6b9d48, 0x4a6b9e00, 0x4ad70000) No shared spaces configured.

Memory Map

The next information in the log is a list of virtual memory regions at the time of the crash. This list can be long if the application is large. The memory map can be very useful when debugging some crashes, because it can tell you which libraries are actually being used, their location in memory, as well as the location of the heap, stack, and guard pages.

The format of the memory map is operating system-specific. On the Oracle Solaris operating system, the base address and library name are printed. On the Linux system, the process memory map () is printed. On the Windows system, the base and end addresses of each library are printed. The following example shows the output generated on Linux/x86.


Most of the lines were omitted from the example for the sake of brevity.
Dynamic libraries: 00400000-00401000 r-xp 00000000 00:47 1374716350 /export/java_re/jdk/9/ea/167/binaries/linux-x64/bin/java 00601000-00602000 rw-p 00001000 00:47 1374716350 /export/java_re/jdk/9/ea/167/binaries/linux-x64/bin/java 016c6000-016e7000 rw-p 00000000 00:00 0 [heap] 82000000-102000000 rw-p 00000000 00:00 0 102000000-800000000 ---p 00000000 00:00 0 40014000-40015000 r--p 00000000 00:00 0 Lines omitted. 7f0f159f8000-7f0f159f9000 r-xp 00000000 08:11 116808980 /export/users/dh198349/tests/hs-err/libMyApp.so 7f0f159f9000-7f0f15bf8000 ---p 00001000 08:11 116808980 /export/users/dh198349/tests/hs-err/libMyApp.so 7f0f15bf8000-7f0f15bf9000 r--p 00000000 08:11 116808980 /export/users/dh198349/tests/hs-err/libMyApp.so 7f0f15bf9000-7f0f15bfa000 rw-p 00001000 08:11 116808980 /export/users/dh198349/tests/hs-err/libMyApp.so Lines omitted. 7f0f15dfc000-7f0f15e00000 ---p 00000000 00:00 0 7f0f15e00000-7f0f15efd000 rw-p 00000000 00:00 0 7f0f15efd000-7f0f15f13000 r-xp 00000000 00:47 1374714565 /export/java_re/jdk/9/ea/167/binaries/linux-x64/lib/libnet.so 7f0f15f13000-7f0f16113000 ---p 00016000 00:47 1374714565 /export/java_re/jdk/9/ea/167/binaries/linux-x64/lib/libnet.so 7f0f16113000-7f0f16114000 rw-p 00016000 00:47 1374714565 /export/java_re/jdk/9/ea/167/binaries/linux-x64/lib/libnet.so 7f0f16114000-7f0f16124000 r-xp 00000000 00:47 1374714619 /export/java_re/jdk/9/ea/167/binaries/linux-x64/lib/libnio.so Lines omitted. 7f0f17032000-7f0f17036000 ---p 00000000 00:00 0 7f0f17036000-7f0f17133000 rw-p 00000000 00:00 0 7f0f17133000-7f0f173fc000 r--p 00000000 08:02 2102853 /usr/lib/locale/locale-archive 7f0f173fc000-7f0f17400000 ---p 00000000 00:00 0 Lines omtted.

The following is a format of memory map in the error log.

40049000-4035c000 r-xp 00000000 03:05 824473 /jdk1.5/jre/lib/i386/client/libjvm.so line gcc make fatal errors encountered - cannot SA_SIGINFO SIGBUS: [libjvm.so+0xd48840], sa_mask[0]=11111111011111111101111111111110, sa_flags=SA_RESTART . . One or the other has to be renamed wherever it is used, in both the flex and byacc files. You can spot exactly which name is the problem by looking for the number given in the error message in the file "y.tab.h" e.g. #define a_number 257

infix_y.y:24: warning: assignment makes integer from pointer without a cast

This, and other, similar errors, may be gcc make fatal errors encountered - cannot by byacc inserting default actions in your program - see section 1.3 on byacc above.

infix_y.y:27: parse error before `int'

One common cause of this error is using the names of the types from your "%union" declaration in "%token" or "%type" declarations instead of the names of the fields e.g. instead of (correct):

%union {int a_number;} %type <a_number> exp term factor %token <a_number> number writing something like (incorrect): %union {int a_number;} %type <int> exp term factor %token <int> number

hundreds of weird error messages about a lex programe.g.

You must not put any spaces or tabs before the patterns in your lex file i.e. not like:

%% [A-Za-z] {printf("%s\n", yytext);} \n


Leave a Comment