[Simh] OpenBSD on Simh VAX 3.8-1 - Segmentation fault

Gregg Levine gregg.drwho8 at gmail.com
Thu Nov 9 04:51:09 EST 2017 

Hello!
I agree. Last time I made my big try it was to first have to track
down and build a copy of tcpdump that would build properly on Eleven.
As I recall releases later then 0.8 for libpcap would in fact be
needed for networking to work properly that way. On Linux of course.
On Windows I simply either made use of the Minimal Cygwin project
build files, and of course the tools, and installed beforehand the
Winpcap library. Or install that library, and then a prebuilt binary
who did do networking.

And I am certainly agreeing with you regarding the job they did
concerning the local customization things for Debian and its ilk.

Anyway if this works I'll need to track down the right methods for
shoehorning DecNet onto it. I've other items. The bigger problem is of
course that of remembering which DEC OS the networking stuff ran well
on....

Incidentally I've corrected the mispelling of the library name. And my
name is exactly as spelled on the signature. The name you posted must
have been an autocorrect mistake.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."


On Thu, Nov 9, 2017 at 2:00 AM, Mark Pizzolato <Mark at infocomm.com> wrote:
> On Wednesday, November 8, 2017 at 9:43 PM, Gregg Levine wrote:
>> Hello!
>> Gary which release  of Slackware Linux was this? I've found that SIMH
>> properly builds on all releases from 7.2 (Which was only released as a Snap
>> Shot Disk from the time of the first shows) all the way the 14.1.
>> I only needed to figure out how to update the LibCap library so that
>> networking would work properly once that arrived not too long ago. As an
>> aside I moved away from trying to build it here on this laptop running 14.2
>> 64bit, because networking requires a fixed connection, not WiFi.
>
> His issues might not have much to do with Slackware, but more to do
> with the version of simh.
>
> The github simh code (4.x) has built easily on most systems for a very long
> time.
>
> Simh 3.9 was reasonable as well but not as robust as the current code.
>
> Simh 3.8-x might have needed local customizations relating to the
> local system environment.  The folks putting together the debian and
> other simh packages certainly messed with the makefile.
>
> - Mark
>
>> -----
>> Gregg C Levine gregg.drwho8 at gmail.com
>> "This signature fought the Time Wars, time and again."
>>
>>
>> On Wed, Nov 8, 2017 at 11:11 AM, Gary Lee Phillips <tivo.overo at gmail.com>
>> wrote:
>> > Thanks for the very clear answer, Mark.
>> >
>> > I followed your instructions and the 4.0-0 beta built in minutes. Last
>> > time I tried to build Simh myself, it took several frustrating days of
>> > patching the makefile and changing references. That was on Slackware
>> > Linux and several versions back of both the environment and Simh. So
>> > thanks ever so much to the developers who have continued to enhance and
>> tune this package.
>> > It is brilliantly done.
>> >
>> > Now the even better news. The vax3900/vax module in 4.0-0 beta does
>> > not have the segmentation fault I encountered with 3.8-1. OpenBSD 5.7
>> > is able to ftp and sftp transfer in and out without any complaints. So
>> > thank you again to whoever it was that found and fixed that problem.
>> >
>> > --Gary
>> >
>> >
>> >
>> > On Wed, Nov 8, 2017 at 1:50 AM, Mark Pizzolato <Mark at infocomm.com>
>> wrote:
>> >>
>> >> Hi Gary,
>> >>
>> >> On Tuesday, November 7, 2017 at 5:29 AM, Gary Lee Phillips wrote:
>> >> > I am running VAX 3.8-1 on a 64-bit Linux system. It performs well
>> >> > with OpenVMS as the operating system. But when I try to run it with
>> >> > OpenBSD 5.7 there are issues.
>> >> >
>> >> > The base system installs and boots correctly. But in order to bring
>> >> > in tools such as language compilers or editors, it is necessary to
>> >> > use ftp or sftp. I cannot get these to transfer anything because
>> >> > the moment a transfer starts, no matter which mode or direction or
>> >> > whether the transfer is initiated from within OpenBSD or from the
>> >> > outside, an immediate segmentation fault occurs. This appears to be
>> >> > within the SimH code itself, and not on OpenBSD.
>> >>
>> >> That would certainly seem to be the case.  Simulator crashes
>> >> definitely should be fixed.  3.8-1 was released some 8 years ago, and
>> >> 3.9 was some 6 years ago.  Both are way behind the current code base
>> >> located at https://github.com/simh/simh/ downloadable as
>> >> https://github.com/simh/simh/archive/master.zip
>> >>
>> >> > The same SimH VAX environment running OpenVMS 7.3 can perform
>> >> > transfers over ethernet without any apparent issues.
>> >>
>> >> This is a useful data point.
>> >>
>> >> > I have tried running SimH in supervisor mode or in user mode, same
>> >> > results. Also same results whether the transfer is initiated by
>> >> > root or by a normal user account.
>> >>
>> >> I wouldn't expect you to be able to run the simulator as non-root and
>> >> have Ethernet functionality...
>> >>
>> >> > The ethernet connection itself seems to be working. Telnet
>> >> > connections function normally, and ftp or sftp will pass directory
>> >> > information and accept commands, but file transfers fail.
>> >> >
>> >> > I guess I could try another version of OpenBSD. Upgrading SimH is
>> >> > also possible but a bit more daunting since 3.8 is what is offered
>> >> > as current on my Linux distro. (Linux Mint 18 "Sarah" 64 bit
>> >> > generic
>> >> > 4.4.0-97)
>> >>
>> >> It really isn't particularly daunting:
>> >>
>> >> First, you'll need the following:
>> >>
>> >>         $ sudo apt install libpcap-dev
>> >> Then:
>> >>         $ wget https://github.com/simh/simh/archive/master.zip
>> >>         $ unzip master.zip
>> >>         $ cd simh-master
>> >>         $ make vax
>> >>         $# Start the newly built simulator:
>> >>         $ BIN/vax
>> >>
>> >>
>> >> If you see any sort of segmentation fault, there is a problem that needs
>> >> fixing, and I'll be glad to address it.   If you have a problem please
>> >> create
>> >> an issue at https://github.com/simh/simh/issues
>> >>
>> >> - Mark
>> >
>> >
>> >
>> > _______________________________________________
>> > Simh mailing list
>> > Simh at trailing-edge.com
>> > http://mailman.trailing-edge.com/mailman/listinfo/simh
>

More information about the Simh mailing list