I am running Slackware 12.0 with the stock gcc (4.1.2) and trying to build Geany 0.12. I get a compiler segfault from the closing brace of create_prefs_dialog in interface.c. this is the last line of the file.
I know it's probably a compiler bug, just wondered if it's a known problem and if there's anything that can be done about it. I've heard it's not very easy to upgrade the compiler. I didn't see anything in Google.
Thanks,
Bob S.
Bob Snyder wrote:
I am running Slackware 12.0 with the stock gcc (4.1.2) and trying to build Geany 0.12. I get a compiler segfault from the closing brace of create_prefs_dialog in interface.c. this is the last line of the file.
I know it's probably a compiler bug, just wondered if it's a known problem and if there's anything that can be done about it. I've heard it's not very easy to upgrade the compiler. I didn't see anything in Google.
Thanks,
Bob S.
Hmm. Strange. I had the same trouble with a couple of other apps and found that after it happened once, it would work okay if I re-ran make. I should have tried that before writing. Not sure what's going on, but it's not nearly as big a problem now.
Bob S.
On Sun, 09 Dec 2007 17:17:38 -0800, Bob Snyder bob.snyder@cox.net wrote:
Bob Snyder wrote:
I am running Slackware 12.0 with the stock gcc (4.1.2) and trying to build Geany 0.12. I get a compiler segfault from the closing brace of create_prefs_dialog in interface.c. this is the last line of the file.
I know it's probably a compiler bug, just wondered if it's a known problem and if there's anything that can be done about it. I've heard it's not very easy to upgrade the compiler. I didn't see anything in Google.
Thanks,
Bob S.
Hmm. Strange. I had the same trouble with a couple of other apps and found that after it happened once, it would work okay if I re-ran make. I should have tried that before writing. Not sure what's going on, but it's not nearly as big a problem now.
No idea what was going on but why don't you use Slackware's gcc version? Which is probably tested to work with the system. Anyway, I don't think this is a bug in gcc itself, more in your setup. But again, no real idea.
Regards, Enrico
Enrico Tröger wrote:
On Sun, 09 Dec 2007 17:17:38 -0800, Bob Snyder bob.snyder@cox.net wrote:
Bob Snyder wrote:
I am running Slackware 12.0 with the stock gcc (4.1.2) and trying to build Geany 0.12. I get a compiler segfault from the closing brace of create_prefs_dialog in interface.c. this is the last line of the file.
I know it's probably a compiler bug, just wondered if it's a known problem and if there's anything that can be done about it. I've heard it's not very easy to upgrade the compiler. I didn't see anything in Google.
Thanks,
Bob S.
Hmm. Strange. I had the same trouble with a couple of other apps and found that after it happened once, it would work okay if I re-ran make. I should have tried that before writing. Not sure what's going on, but it's not nearly as big a problem now.
No idea what was going on but why don't you use Slackware's gcc version? Which is probably tested to work with the system. Anyway, I don't think this is a bug in gcc itself, more in your setup. But again, no real idea.
This is the version of gcc (4.1.2) that comes stock with Slack 12.0. It seems to be erratic, segfaulting in maybe one out of three builds. Here's what I see when it happens:
g++ -DHAVE_CONFIG_H -I. -I.. -I.. -I./include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12 -DNDEBUG -Os -DGTK -DGTK2 -DSCI_LEXER -DG_THREADS_IMPL_NONE -g -O2 -MT Editor.o -MD -MP -MF .deps/Editor.Tpo -c -o Editor.o Editor.cxx Editor.cxx:7419: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. make[3]: *** [Editor.o] Error 1 make[3]: Leaving directory `/home/downloads/geany-0.12/scintilla' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/downloads/geany-0.12/scintilla' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/downloads/geany-0.12' make: *** [all] Error 2
This is at the closing brace of a very large function (~1750 lines in scintilla's Editor.cxx) so maybe it's overflowing the stack or something.
I wouldn't be surprised if it's something in my setup, but it's pretty stock. A Dell Dimension 9150, 1GB RAM, Xfce 4.4.1, Pentium D, nothing much changed from the Slack install.
Bob S.
Bob Snyder wrote:
This is the version of gcc (4.1.2) that comes stock with Slack 12.0. It seems to be erratic, segfaulting in maybe one out of three builds.
Are you sure, that your hardware is OK? I have seen such errors just before my processor died...
Best regards Andreas
On Mon, 17 Dec 2007 07:48:36 +0100, Andreas Tscharner andy@vis.ethz.ch wrote:
Bob Snyder wrote:
This is the version of gcc (4.1.2) that comes stock with Slack 12.0. It seems to be erratic, segfaulting in maybe one out of three builds.
Are you sure, that your hardware is OK? I have seen such errors just before my processor died...
Yes or it might be your RAM. Try compiling a kernel(2.6.xx), this should do any gcc and if not consider running memtest86 on your machine to verify your RAM.
Regards, Enrico
On Mon, 17 Dec 2007 15:57:11 +0100 Enrico Tröger enrico.troeger@uvena.de wrote:
On Mon, 17 Dec 2007 07:48:36 +0100, Andreas Tscharner andy@vis.ethz.ch wrote:
Bob Snyder wrote:
This is the version of gcc (4.1.2) that comes stock with Slack 12.0. It seems to be erratic, segfaulting in maybe one out of three builds.
Are you sure, that your hardware is OK? I have seen such errors just before my processor died...
Yes or it might be your RAM. Try compiling a kernel(2.6.xx), this should do any gcc and if not consider running memtest86 on your machine to verify your RAM.
Good idea. But keep in mind, if memtest finds any failure, your RAM is really broken. If it doesn't find any, it doesn't mean on the other hand that your RAM is really OK.
Regards, Frank
Frank Lanitz wrote:
On Mon, 17 Dec 2007 15:57:11 +0100 Enrico Tröger enrico.troeger@uvena.de wrote:
On Mon, 17 Dec 2007 07:48:36 +0100, Andreas Tscharner andy@vis.ethz.ch wrote:
Bob Snyder wrote:
This is the version of gcc (4.1.2) that comes stock with Slack 12.0. It seems to be erratic, segfaulting in maybe one out of three builds.
Are you sure, that your hardware is OK? I have seen such errors just before my processor died...
Yes or it might be your RAM. Try compiling a kernel(2.6.xx), this should do any gcc and if not consider running memtest86 on your machine to verify your RAM.
Good idea. But keep in mind, if memtest finds any failure, your RAM is really broken. If it doesn't find any, it doesn't mean on the other hand that your RAM is really OK.
Regards, Frank
After noticing some other anomalies including a total lockup of the machine, I ran memtest86 and indeed it found errors. I have ordered some new SIMMs. Good excuse for an upgrade to more RAM! I'll update the list when I've tried it.
Thanks for the advice.
Bob S.
On Sun, 09 Dec 2007 11:53:20 -0800 Bob Snyder bob.snyder@cox.net wrote:
I am running Slackware 12.0 with the stock gcc (4.1.2) and trying to build Geany 0.12. I get a compiler segfault from the closing brace of create_prefs_dialog in interface.c. this is the last line of the file.
I know it's probably a compiler bug, just wondered if it's a known problem and if there's anything that can be done about it. I've heard it's not very easy to upgrade the compiler. I didn't see anything in Google.
I'm using 4.1.2/4.1.3 -see below- too, but I never had this problems.
frank@Eco Mo 10 Dez 2007 22:34:08 CET (3772)~/quellen/svn/geany/trunk> gcc --version gcc (GCC) 4.1.3 20070629 (prerelease) (Debian 4.1.2-13) Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Strange thing.
Regards, Frank
Frank Lanitz wrote:
On Sun, 09 Dec 2007 11:53:20 -0800 Bob Snyder bob.snyder@cox.net wrote:
I am running Slackware 12.0 with the stock gcc (4.1.2) and trying to build Geany 0.12. I get a compiler segfault from the closing brace of create_prefs_dialog in interface.c. this is the last line of the file.
I know it's probably a compiler bug, just wondered if it's a known problem and if there's anything that can be done about it. I've heard it's not very easy to upgrade the compiler. I didn't see anything in Google.
I'm using 4.1.2/4.1.3 -see below- too, but I never had this problems.
frank@Eco Mo 10 Dez 2007 22:34:08 CET (3772)~/quellen/svn/geany/trunk> gcc --version gcc (GCC) 4.1.3 20070629 (prerelease) (Debian 4.1.2-13) Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Strange thing.
Regards, Frank
Looks like yours is a bit newer. Mine says:
$ g++ --version g++ (GCC) 4.1.2 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Bob S.
Hi,
On Sun, 16 Dec 2007 18:14:05 -0800 Bob Snyder bob.snyder@cox.net wrote:
Frank Lanitz wrote:
On Sun, 09 Dec 2007 11:53:20 -0800 Bob Snyder bob.snyder@cox.net wrote:
I am running Slackware 12.0 with the stock gcc (4.1.2) and trying to build Geany 0.12. I get a compiler segfault from the closing brace of create_prefs_dialog in interface.c. this is the last line of the file.
I know it's probably a compiler bug, just wondered if it's a known problem and if there's anything that can be done about it. I've heard it's not very easy to upgrade the compiler. I didn't see anything in Google.
I'm using 4.1.2/4.1.3 -see below- too, but I never had this problems.
frank@Eco Mo 10 Dez 2007 22:34:08 CET (3772)~/quellen/svn/geany/trunk> gcc --version gcc (GCC) 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)
Looks like yours is a bit newer. Mine says:
$ g++ --version g++ (GCC) 4.1.2
Yes. You are right. I just was looking at the Debian. 4.1.2-13 entry ;D
Regards, Frank