<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body >Tou ca n also try llvm on the Linux side,<br><br><br>-------- Original message --------<br>From Michael Huff <mphuff@gmail.com> <br>Date: 02/17/2016 1:15 PM (GMT-07:00) <br>To simh@trailing-edge.com <br>Subject Re: [Simh] Recent build crashes on OSX <br> <br><br>On 2/17/16 11:07 AM, Timothe Litt wrote:<br>> On 17-Feb-16 14:59, Paul Koning wrote:<br>>>> On Feb 17, 2016, at 2:53 PM, Timothe Litt <litt@ieee.org> wrote:<br>>>><br>>>> On 17-Feb-16 14:48, Michael Huff wrote:<br>>>>> I grabbed simh_master.zip from github yesterday and compiled it on OSX<br>>>>> and in a virtualbox instance of Linux Mint 17. OSX is the native OS,<br>>>>> Linux is in a VM.<br>>>>><br>>>>> I have a 43BSD machine accessible to both on a shared drive. It will<br>>>>> boot normally when I run vax780 inside of the Linux VM, but when I<br>>>>> run the vax780 binary I compiled in OSX it crashes.<br>>>>><br>>>> If I had to guess, it would be that the shared drive is not presenting<br>>>> the same data to both environments.<br>>>><br>>>> Perhaps it's treating the binary file as text and adding <CR><LF>s -- or<br>>>> some such.<br>>>><br>>>> I'd checksum the file from both sides before assuming it's a SimH issue.<br>>> That is a good test, certainly. But OSX is Unix, so it shouldn't suffer from the sort of Windows-style misbehavior you mentioned.<br>> I know. But it does depend on how the file is shared, and from where.<br>> Is the real file on OSX? On Windows? On an NAS? Shared over SMB? NFS?<br>The file is on an external hard disk formatted as NTFS; I have a device <br>driver installed on OSX to make the filesystem read/write, and it's <br>mounted as a shared folder in virtualbox.<br>> Especially SMB has been known to do very strange things.<br>><br>> Well, I see that md5sums match, so it's not that this time.<br>>> I wonder if it might be a compiler bug. It would be instructive to download gcc and use that to build the OSX based SIMH, to see if it behaves differently.<br>> Yup.<br>><br>> The symptom looks like data corruption. The instruction at the faulting<br>> PC is not likely a real one.<br>><br>>> paul<br>>><br>>><br>I built it in Linux with gcc 4.8; I'm trying to install gcc 4.8 in <br>macports on OSX but it has to compile which will probably take some <br>time. After it's done I'll recompile simh and see if it works then.<br><br>_______________________________________________<br>Simh mailing list<br>Simh@trailing-edge.com<br>http://mailman.trailing-edge.com/mailman/listinfo/simh</body>