From: Finn Thain <fthain@telegraphics.com.au>
To: Rob Landley <rob@landley.net>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
linux-m68k@vger.kernel.org, Laurent Vivier <Laurent@Vivier.EU>
Subject: GCC?, was Re: Running m68k on qemu with external initramfs?
Date: Mon, 13 Apr 2020 09:30:40 +1000 (AEST) [thread overview]
Message-ID: <alpine.LNX.2.22.394.2004130922090.8@nippy.intranet> (raw)
In-Reply-To: <238ea76c-fa8e-0134-667b-3864938d9a78@landley.net>
On Sun, 12 Apr 2020, Rob Landley wrote:
>
> 2) THEN the problem was that gcc is doing something in cd_main so that
> the "chdir ." at the start of the shell setup (to set $PWD and friends)
> is segfaulting, but it's a segfault that went away when I got near it
> with printf() calls, and even write(1, "", 0); right before it made it
> go away. Given that this code has run on 32 and 64 bit, big and little
> endian, glibc musl and bionic, and on a target that's both nommu and
> cares about alignment?
Are you sure that "gcc is doing something [wrong]"? Do you think it could
be a QEMU bug? Can you provide some information about your tool chain?
>
> Because I'm still halfway through teaching toysh about all the ${}
> constructs. (Also, remind me to stick echo -e '\e[?7h' at the start of
> my init script to undo the STUPID wordwrap disable escape that qemu's
> bios outputs, which screws up bash's command line history too!)
How awful. It baffles me every time bash manages to mishandle unprintable
output from a command such that it somehow becomes command line input
which bash then attempts to execute! I wish I knew how to prevent that.
next prev parent reply other threads:[~2020-04-12 23:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 0:50 Running m68k on qemu with external initramfs? Rob Landley
2020-04-11 6:12 ` Finn Thain
2020-04-12 3:36 ` Rob Landley
2020-04-12 5:29 ` Finn Thain
2020-04-12 12:34 ` Rob Landley
2020-04-12 8:27 ` John Paul Adrian Glaubitz
2020-04-12 8:31 ` Laurent Vivier
2020-04-12 21:48 ` Rob Landley
2020-04-12 23:17 ` Finn Thain
2020-04-11 12:12 ` John Paul Adrian Glaubitz
2020-04-12 12:48 ` Rob Landley
2020-04-12 13:02 ` John Paul Adrian Glaubitz
2020-04-12 21:56 ` Rob Landley
2020-04-12 23:30 ` Finn Thain [this message]
2020-04-13 0:28 ` GCC?, was " Rob Landley
2020-04-13 5:17 ` Finn Thain
2020-04-13 7:07 ` Rob Landley
2020-04-13 7:41 ` John Paul Adrian Glaubitz
2020-04-13 8:27 ` Rob Landley
2020-04-13 9:42 ` Geert Uytterhoeven
2020-04-13 23:02 ` Finn Thain
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=alpine.LNX.2.22.394.2004130922090.8@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=Laurent@Vivier.EU \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-m68k@vger.kernel.org \
--cc=rob@landley.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 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 NNTP newsgroup(s).