public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dafrabbit at yahoo dot com" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/366] New: Compiling on 64-bit yields segmentation fault when run, on 32-bit runs fine.
Date: Fri, 03 Sep 2004 02:39:00 -0000	[thread overview]
Message-ID: <20040903023911.366.dafrabbit@yahoo.com> (raw)

Compiling a small C program in 64-bit mode with gcc, compiling is fine, but when
run the program seg faults. Same program, compiled in 32-bit mode with gcc runs
fine. Bug report posted in gcc Bugzilla, told to repost here. (link to gcc bug
report: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17302)

Building on an Athlon64, gcc version 3.4.1-9, glibc version 2.3.3-27, kernel
version 2.6.5-1.358.

To reproduce:
1. gcc -g test_var5.c
2. gcc -o test5.exe test_var5.o
3. test5.exe

The program is attached.

-- 
           Summary: Compiling on 64-bit yields segmentation fault when run,
                    on 32-bit runs fine.
           Product: glibc
           Version: 2.3.3
            Status: NEW
          Severity: normal
          Priority: P1
         Component: libc
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: dafrabbit at yahoo dot com
                CC: glibc-bugs at sources dot redhat dot com


http://sources.redhat.com/bugzilla/show_bug.cgi?id=366

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2004-09-03  2:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-03  2:39 dafrabbit at yahoo dot com [this message]
2004-09-03  2:39 ` [Bug libc/366] " dafrabbit at yahoo dot com
2004-09-03  4:23 ` aj at suse dot de
2004-09-03  7:41 ` jakub at redhat dot com
2004-09-03 13:01 ` dafrabbit at yahoo dot com

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=20040903023911.366.dafrabbit@yahoo.com \
    --to=sourceware-bugzilla@sources.redhat.com \
    --cc=glibc-bugs@sources.redhat.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).