Hi DM,

I recently migrated my setup to a virtual disk from a physical Ubuntu Linux setup. On the virtual setup, everytime I would fire up sbbs, it would end up aborting with 'illegal instruction'. This would happen even after doing a full clean and rebuild, and even with newly pulled code from cvs. I enabled core dumps, but that didn't reveal much because I had compiled using RELEASE=1. So,
I did another full clean and recompiled with DEBUG=1 instead, hoping to get a core that might point to something.

the debug compile doesn't dump core, doesn't abort with 'illegal instruction'. It runs fine.

I did another clean and just changed my compile line back: 'make RELEASE=1 USE_DOSEMU=1 install' . I get illegal instruction and the program aborts. I am
starting everything as 'root' user

I clean and recompile again: 'make DEBUG=1 USE_DOSEMU=1 install' , everything works.

I've done this enough times and it's consistent everytime.

Might you have insights based on the limited info I just posted about why a debug build wouldn't have the same issues as a release build? At this point, I'm fine just running debug build, just curiosity. I'm randomly guessing some sort of optimization being done during the release compile isn't sitting well with the VMware virtualization. Is there a way to change the optimization settings for the release build 'easily' or would I need to find each makefile and edit those individually ?

--
H
... I'm not anti-social; I'm just not user friendly.
--- MultiMail/Win v0.52
þ Synchronet þ - Running madly into the wind and screaming - bbs.ujoint.org
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: release vs debug
By: Hemo to Digital Man on Wed Aug 19 2020 09:20 am

Might you have insights based on the limited info I just posted about why a debug build wouldn't have the same issues as a release build?

No, but my first suspicion would be the VM manager or VM configuration is at fault.

At this
point, I'm fine just running debug build, just curiosity. I'm randomly guessing some sort of optimization being done during the release compile isn't sitting well with the VMware virtualization. Is there a way to

change

the optimization settings for the release build 'easily' or would I need to find each makefile and edit those individually ?

I'd just run debug (I do).

digital man

This Is Spinal Tap quote #27:
As long as there's, y'know, sex and drugs, I can do without the rock and roll. Norco, CA WX: 98.2øF, 40.0% humidity, 6 mph NE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.11-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: release vs debug
By: Digital Man to Hemo on Wed
Aug 19 2020 12:20 pm

Might you have insights based on the limited info I just posted about
why a debug build wouldn't have the same issues as a release build?

No, but my first suspicion would be the VM manager or VM configuration is at fault.

I'd just run debug (I do).

that's what I think I'm going to do. Path of least resistance and all.
thanks for the feedback.
-
H

... I got some powdered water, but I don't know what to add.

---
þ Synchronet þ - Running madly into the wind and screaming - bbs.ujoint.org
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)