public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: aaboulhosn@entpm2.prod.fedex.com
Cc: Help-gcc@gnu.org
Subject: Re: Core Dump , when running ./a.out
Date: Wed, 28 Feb 2001 07:40:00 -0000	[thread overview]
Message-ID: <orae76hl4i.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <OF09BA32DC.7B6FD76C-ON86256A01.00551AC1@prod.fedex.com>

On Feb 28, 2001, aaboulhosn@entpm2.prod.fedex.com wrote:

> Thank you for responding...
> 1) When, I try to run ./a.out
>        it complains about , libucb.so.1  not found
>       So, I tried :
>      ld  -R  /usr/ucblib

>     and it does not complain any more about that problem.
>    Then I try to run :  ./a.out it cores dump.

But why are you linking with libucb?

The core dump might stem from some incompatibility between libucb and
whatever other libraries are getting linked in.

BTW, is this with GNU as/ld or the native assembler and linker?  How
was GCC configured?

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

  reply	other threads:[~2001-02-28  7:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-28  7:36 aaboulhosn
2001-02-28  7:40 ` Alexandre Oliva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-28  8:18 David Korn
2001-02-28  7:51 aaboulhosn
2001-02-28  8:03 ` Abdelshakour Abuzneid
2001-02-28  9:57 ` Alexandre Oliva
2001-02-28  7:29 aaboulhosn
2001-02-28  5:44 aaboulhosn
2001-02-28  7:11 ` sherry
2001-02-28  7:23 ` Alexandre Oliva
2001-02-27 10:24 aaboulhosn
2001-02-27  6:09 aaboulhosn
2001-02-26 10:41 aaboulhosn

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=orae76hl4i.fsf@guarana.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=Help-gcc@gnu.org \
    --cc=aaboulhosn@entpm2.prod.fedex.com \
    /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).