public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Yusuf Goolamabbas <yusufg@krdl.org.sg>
To: egcs@cygnus.com
Subject: PGP 5.0i compiled with egcs-1.0.2/Solaris 2.6-sparc gives bus error
Date: Tue, 24 Mar 1998 00:03:00 -0000	[thread overview]
Message-ID: <199803240715.PAA27590@charlotte.krdl.org.sg> (raw)

When generating a key via pgpk -g. I get a bus error.

According to the PGP bugs page

http://www.pgpi.com/bugs/bugs50i.shtml

Bus error on Solaris 2.5.1
Kris Van Hees <aedil@ny.fnx.com> wrote:

Hi,
    Compiling PGP 5.0i sources on a Solaris 2.5.1 (Sparc20) box with
GCC 2.7.1 succeeded but the resulting code aborts with a Bus Error when
running key generation (pgpk -g).  I traced down the problem to the struct
MD5Context, which contains a conditional for HAVE64, which is set along
with typedefs in include/pgpUsuals.h.  I am not certain why, but using
that auto-resolving finds a 64bit type as 'unsigned long long', and thus
sets HAVE64.  Yet when used in code this fails.  I think this might be
a problem with GCC/Solaris interaction.  A Bus Error sounds to me as a
possible alignment problem there.

        I manually disabled the HAVE64 check, so that the code will use
two 32bit words, and that solved the problem.

Can somebody comment upon this ?

I am on a solaris-sparc-2.6 system with gcc
gcc version egcs-2.90.27 980315 (egcs-1.0.2 release)

Cheers, Yusuf
-- 
Kent Ridge Digital Labs (Formerly Institute of Systems Science)
Heng Mui Keng Terrace, Singapore 119597, Republic of Singapore
Tel: +65 874-3116, Fax: +65 774-4990,  Email: yusufg@krdl.org.sg

             reply	other threads:[~1998-03-24  0:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-24  0:03 Yusuf Goolamabbas [this message]
1998-03-27 15:18 ` Todd Vierling
1998-03-26 23:46 Geoffrey KEATING

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=199803240715.PAA27590@charlotte.krdl.org.sg \
    --to=yusufg@krdl.org.sg \
    --cc=egcs@cygnus.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).