All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Berndtsson <stefan@nocrew.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: xine, ppc and illegal instructions
Date: 24 Mar 2001 00:53:54 +0100	[thread overview]
Message-ID: <87bsqs59f1.fsf@hades.nocrew.org> (raw)


I tried compiling xine-0.4.01 with the ppc-patches by Henry Worth.
Compiling went fine.

When running the resulting binary, I end up with an Illegal instruction.
It doesn't seem to matter what mpegfile I try to use it on, so I assume
it dies before messing with the mpeg.

An strace of the program gives this at the end:

open("/usr/local/lib/xine/plugins/input_net.so", O_RDONLY) = 9
read(9, "\177ELF\1\2\1\0\0\0\0\0\0\0\0\0\0\3\0\24\0\0\0\1\0\0\v"..., 1024) = 1024
SYS_197(0x9, 0x7fffec40, 0x7fffec40, 0x101f3170, 0) = 0
mmap(0xf993000, 71456, PROT_READ|PROT_EXEC, MAP_PRIVATE, 9, 0) = 0xf993000
mprotect(0xf995000, 63264, PROT_NONE)   = 0
mmap(0xf9a3000, 8192, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 9,
0) = 0xf9a3000
close(9)                                = 0
mprotect(0xf993000, 8192, PROT_READ|PROT_WRITE) = 0
mprotect(0xf993000, 8192, PROT_READ|PROT_EXEC) = 0
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++


Kernel version is 2.4.0, with some dmasound-patches applied.
Distribution is Debian (reasonably fresh).
Glibc 2.2.2-1

The binary has been compiled both with and without optimisations, with no
appearent difference.

The above could hint that input_net.so was a problem, so I removed that one,
and then just the next input showed up with a more or less identical trace.
Is this a libc problem? Is it something else? I have no idea where to look.
Since I can't even get a coredump to look in, I guess this isn't really in
the binary.

/Stefan

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2001-03-23 23:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-23 23:53 Stefan Berndtsson [this message]
2001-03-24  0:09 ` xine, ppc and illegal instructions Gregorio Gervasio Jr.
  -- strict thread matches above, loose matches on Subject: below --
2001-03-24  4:58 Henry Worth
2001-03-24 10:57 ` Stefan Berndtsson
2001-03-24  6:13 Henry Worth
2001-03-24 19:17 Henry Worth
2001-03-27  5:30 Bill Fink
     [not found] <Pine.LNX.4.21.0103262330001.19578-100000@gwiz.nasa.atd.net >
2001-03-27 13:41 ` Franz Sirl
2001-04-01 17:51   ` Bill Fink
2001-04-01 19:39     ` Michel Dänzer
2001-04-01 21:08       ` Bill Fink
2001-04-01 20:02     ` Kevin B. Hendricks
2001-04-01 20:12       ` Benjamin Herrenschmidt
2001-04-01 21:24       ` Bill Fink
2001-04-02 11:50         ` Kevin B. Hendricks
2001-03-30  5:20 Henry Worth
2001-03-30  5:29 ` David Edelsohn
2001-03-30 14:59   ` Henry Worth
2001-03-30  5:26 Henry Worth
2001-03-31 20:16 ` Bill Fink

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=87bsqs59f1.fsf@hades.nocrew.org \
    --to=stefan@nocrew.org \
    --cc=linuxppc-dev@lists.linuxppc.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 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.