In my building of Slack/390, I've run across this any number of times. Sometimes, simply re-compiling with a lower level of optimization (instead of -O2, use -O1, -O0, etc.) can fix things. At other times, putting on gcc or glibc fixes were required.
As others have suggested, running under gdb is sometimes helpful. Since compiling with -g and running under gdb caused your problem to go away, you could just compile as normal, and still run under gdb to see if that replicates the problem. You don't get as much human-readable information as compiling with -g gives you, but in your case you're not getting anything at all, now. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Bishop, Peter G Sent: Wednesday, March 22, 2006 7:51 PM To: [email protected] Subject: dumb porting question about seg faults -snip- I thought seg faults are kind of like S0C4s in "traditional" MVS abend terms, i.e. you're treading somewhere you shouldn't. I've bumped up the VM size of this guest to its max of 2G (it's a 31-bit guest) and still the seg fault happens. Can anyone suggest a reason why a seg fault might happen on one platform but not another? Please excuse my ignorance if I've phrased the question badly. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
