From: anand@eis.iisc.ernet.in (SVR Anand)
To: gcc@gcc.gnu.org
Subject: gcc comes out with Aborted
Date: Wed, 24 Sep 2003 18:34:00 -0000 [thread overview]
Message-ID: <200309241457.UAA00758@eis.iisc.ernet.in> (raw)
Hi,
I am unable to compile any program with gcc on my Linux machine. gcc comes out
with "Aborted" message.
Is there a way out ? Please help me.
Anand
The details of the environment follow. I hope this information is sufficient.
--------------------------------------------------------------------
System : RedHat 7.2, Intel P4.
--------------------------------------------------------------------------
# gcc -v -save-temps abc.c
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)
/usr/lib/gcc-lib/i386-redhat-linux/2.96/cpp0 -lang-c -v -D__GNUC__=2 -D__GNUC_MINOR__=96 -D__GNUC_PATCHLEVEL__=0 -D__ELF__ -Dunix -Dlinux -D__ELF__ -D__unix__ -D__linux__ -D__unix -D__linux -Asystem(posix) -D__NO_INLINE__ -Acpu(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ -D__tune_i386__ abc.c abc.i
GNU CPP version 2.96 20000731 (Red Hat Linux 7.1 2.96-98) (cpplib) (i386 Linux/ELF)
ignoring nonexistent directory "/usr/i386-redhat-linux/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/local/include
/usr/lib/gcc-lib/i386-redhat-linux/2.96/include
/usr/include
End of search list.
Aborted
--------------------------------------------------------------------------
The program I am trying out.
#cat abc.c
main()
{
}
--------------------------------------------------------------------------
gdb dump
--------
#gdb gcc
(gdb) r abc.c
Starting program: /usr/bin/gcc abc.c
Program received signal SIGABRT, Aborted.
0x4005aa01 in __kill () from /lib/i686/libc.so.6
(gdb) bt
#0 0x4005aa01 in __kill () from /lib/i686/libc.so.6
#1 0x4005a7da in raise (sig=6) at ../sysdeps/posix/raise.c:27
#2 0x4005bf82 in abort () at ../sysdeps/generic/abort.c:88
#3 0x0804bca9 in strcpy ()
#4 0x0804f02e in strcpy ()
#5 0x08050c37 in strcpy ()
#6 0x08050201 in strcpy ()
#7 0x08050c37 in strcpy ()
#8 0x08050201 in strcpy ()
#9 0x08050c37 in strcpy ()
#10 0x08050201 in strcpy ()
#11 0x0804ecba in strcpy ()
#12 0x080524b1 in strcpy ()
#13 0x40048507 in __libc_start_main (main=0x8051240 <strcpy+32088>, argc=3,
ubp_av=0xbffffb24, init=0x8049050, fini=0x80560d0 <__umoddi3+496>,
rtld_fini=0x4000dc14 <_dl_fini>, stack_end=0xbffffb1c)
at ../sysdeps/generic/libc-start.c:129
(gdb)
next reply other threads:[~2003-09-24 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 18:34 SVR Anand [this message]
2003-09-25 8:44 ` Jim Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200309241457.UAA00758@eis.iisc.ernet.in \
--to=anand@eis.iisc.ernet.in \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).