All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6566] New: PHP segfault when crosscompiled to mips64
Date: Fri, 18 Oct 2013 23:28:35 +0000 (UTC)	[thread overview]
Message-ID: <bug-6566-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=6566

           Summary: PHP segfault when crosscompiled to mips64
           Product: buildroot
           Version: 2013.08
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: cassiano at idbinfo.com.br
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created attachment 5084
  --> https://bugs.busybox.net/attachment.cgi?id=5084
endian fix

PHP crashes with a segfault when compiled do mips64r2 n32.

Any function related to timezone gives a segfault, like date(), gettimeofday(),
and some other random errors, like microtime() dumping garbage on the screen.

I found out that autoconf did not set some macros when configuring, resulting
little endian code being compiled to a big endian machine.

A simple test can be done on a mips64 machine:

php -r 'print_r(date('l'));'

Result in segfault instantly.

Attached is a patch that solves this issue.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2013-10-18 23:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18 23:28 bugzilla at busybox.net [this message]
2013-10-23  1:46 ` [Buildroot] [Bug 6566] PHP segfault when crosscompiled to mips64 - patch included bugzilla at busybox.net
2013-10-23 22:46 ` bugzilla at busybox.net

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=bug-6566-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.