GCC segmentation fault error driving me nuts..

I would be a very happy chappy if anyone could tell me how too avoid the segmentation fault error I keep getting with gcc ( recent ELF build ). Switching from static lib sometimes helps, but then I get the error elsewhere. I cant remember getting the problem so much from the older gcc3, but after switching I get the file ‘cc1xxx’ not found error.
- I cant remember the exact name. I think the fix for that was easy, but I cant remember it if anyone would kindly shed some light.

I usually use the Norcroft compiler as I couldn’t be without DeskDebug but my colleagues like to use the STL, forcing me to use gcc. I’ve never got templates or the cathlib to work properly with cfront, and was considering writing a preprocessor that would create the extra source like the later cfront did – Would this be of any use to anybody? Saying that I would rather see it done properly by RISC OS OPEN…

More importantly this segmentation fault is costing my hours of waste, so please any help would be grately appreciated..

Thanks in advance,

Matt

My apologies – the bug was on me this time. I’m still sure the gcc has some issues there though…

Regarding templates am I the only one who would like to see them supported? Does the latest version of the DDE have better support?

Matt

p.s that wasn’t a shout in my previous message – perhaps ‘ROOL’ would have been more appropriate – I was merely copying the title above..

Regarding templates am I the only one who would like to see them supported?

In what way? Do you mean with a template editor like FormED? If you do, I mentioned it recently, but I didn’t follow up by discovering where it can be got from.

If you don’t mean with a template editor, then what do you mean?

There’s no change in Acorn C++

He means C++ templates – part of the language.

Cfront in DDE is from 1991, and Cfront itself was abandoned in 1993. So I wouldn’t assume that anything’s ever going to happen on the Cfront front¹.

If you’re having trouble with GCC, can you explain the problems? The RISC OS GCC mailing list is usually able to solve problems like this. Specifically, cc1 and cc1plus are C and C++ compiler backends so if you don’t have those you probably didn’t download and unpack all the bits correctly.

¹ The Cfront front front – the public face of a shadowy movement to bring back early 1990s compilers

The Cfront front front – the public face of a shadowy movement to bring back early 1990s compilers

Oooh, yes! TurboC and Memory Models… What’s near and what’s far? The hell kind of program wants 1Mb for code but only 64K for data and stack? Can anybody remember the quirky keypresses? Shift-Del and Shift-Ins for cut and paste; or Ctrl-Ins to copy. Hmmm!

[and in the opposite corner, Zap and Norcroft C – I have the feeling this might be a brief Curb-Stomp Battle]

The Cfront front front

Splitters!

Regarding cfront, rool does have the source, although don’t seem too intent on improving it – maybe because the OS is written in C.. (and maybe also because cfront works on oldskool C). It’s a shame the later versions were not licensed, as they were quite good and supported templates quite efficiently by creating the extra source. What confuses me is Cathlib (an STL specifically for cfront); which looks very impressive if only I could get it to work…

My main issues regarding gcc is it’s slow and doesn’t have a debugger, although my current problem is attempting to use gcc generated tools with make (as DDE extensions). My code just crashes and burns when attempting to link with the sharedClib, and also I’m left without the unix library – Does anyone know where I can download the unix lib source, or the complete pre-elf gcc ( v3 )? Its strange – when !Make calls a unixlib linked binary (static or non static / aif or ELF ), it won’t even manage a hello world – it just goes into a loop and I have to hit Alt-Del. I’m presuming this is something to do with the cmdline extention, but I don’t even get the chance to try calling ddeutils_getcl… I will try the gcc forum, but I can see myself having to write a small sharedc program to dump the cmd line args to file and read that from my unixlib compiled binary – yuck. Does anyone know how !Make / frontEnd launch its tools? Does the 256 cmdline limit still exist? Any related info on !Make / FrontEnd would be appreciated – btw the tools work fine individually with frontend (or any other way), but not with ‘!Make’… ??

Thanks in advance, and sorry if the above isn’t too clear, my heads all over the place after battling with gcc..

Matt