ooc-compiler

Re: [ooc-compiler] Segmentation fault during installation

[Jan <juh...@mn...>]

Michael van Acken wrote:
> For some reasons I currently do not get any mails from ooc-compiler,
> but Tim kindly forwarded this to me:
> 
>>[...]
>>gc6.1 seems to have installed smoothly (including make check). My only
>>modification was that since including gc.h didn't work the way
>>described in INSTALL (using CPPFLAGS), I copied the contents of
>>gc/include to /usr/local/include/gc instead.
> 
> 
> Segfaults like this are usually caused by bad interaction with the
> gc.  I would suggest to try to build first without gc (it should be
> sufficient to move the gc headers out of the may, then "make
> distclean", then "configure").  The build may run out of memory, but
> repeated "make" should do the trick.
> 
> If this works out, a more recent gc may get you further.

Hi Michael,
I tried the solution you suggested. I renamed gc.h and libgc.*, so that 
configure wouldn't use them - the results are the same as described in 
my first post.

At the moment, I think the problem must be be related to my distribution 
(SuSE 9.0 professional): I just finished trying installation on a 
different machine at work that's running the same distribution (without 
gc) with exactly the same results and behaviour that I get here at home.

Is there anyone using SuSE 9.0 who installed oo2c successfully? Are 
there any libs or programs used during installation that might be 
missing/corrupt/wrong version in SuSE 9.0?

Jan

Re: [ooc-compiler] Segmentation fault during installation

[Stewart G. <sgr...@ii...>]

Hi Jan,

Two suggestions:

1) Try running the executable that fails under gdb. That should 
indicate the context in which the problem occurs.

2) Recent versions of the GC seem to default to building threaded 
collectors. On some platforms it is necessary to specify particular 
flags when compiling the _client_ code. If you have a threaded GC, you 
will probably have to specify "-DGC_LINUX_THREADS" in CPPFLAGS, or 
something like that. I don't know about Linux, but this is certainly 
necessary under Windows and Mac OS X (see README.{MACOS,WIN32} for 
discussion). Omitting the client flags can cause things to go horribly 
wrong.

Cheers,
   Stewart

On Tuesday, February 10, 2004, at 09:03 AM, Jan wrote:

> Michael van Acken wrote:
>> For some reasons I currently do not get any mails from ooc-compiler,
>> but Tim kindly forwarded this to me:
>>> [...]
>>> gc6.1 seems to have installed smoothly (including make check). My 
>>> only
>>> modification was that since including gc.h didn't work the way
>>> described in INSTALL (using CPPFLAGS), I copied the contents of
>>> gc/include to /usr/local/include/gc instead.
>> Segfaults like this are usually caused by bad interaction with the
>> gc.  I would suggest to try to build first without gc (it should be
>> sufficient to move the gc headers out of the may, then "make
>> distclean", then "configure").  The build may run out of memory, but
>> repeated "make" should do the trick.
>> If this works out, a more recent gc may get you further.
>
> Hi Michael,
> I tried the solution you suggested. I renamed gc.h and libgc.*, so 
> that configure wouldn't use them - the results are the same as 
> described in my first post.
>
> At the moment, I think the problem must be be related to my 
> distribution (SuSE 9.0 professional): I just finished trying 
> installation on a different machine at work that's running the same 
> distribution (without gc) with exactly the same results and behaviour 
> that I get here at home.
>
> Is there anyone using SuSE 9.0 who installed oo2c successfully? Are 
> there any libs or programs used during installation that might be 
> missing/corrupt/wrong version in SuSE 9.0?
>
> Jan
>
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> ooc-compiler mailing list
> ooc...@li...
> https://lists.sourceforge.net/lists/listinfo/ooc-compiler
>

Re: [ooc-compiler] Segmentation fault during installation

[Tim T. <ra...@ed...>]

Hallo!

Another suggestion. What threading library do you use. Suse 9.0 might be =

prepared for Kernel 2.6.x and thus might not have choosen the classic=20
pthreads package but the new three letter acronym version (LWT or=20
something like that). This may interfere witht he gc. You should be able =

to find that out by doing an ldd on the libgc.so.

You should also do an ldd on the oo2c binary that is used during the=20
build to find out if it is linked against the gc, but I think you=20
already have proven that.

Is the crash reproducable? Do you always get the same call stack when=20
you try to compile (using gdb) or is the call stack random. If it is=20
random, Michaels guess that this is a problem with the gc is more=20
likely, if is always stays the same, it is more likely that there is a=20
bug in the compiler (speaking of 60/40 or 70/30 and reverse). Ahhh,=20
Michael, did you use that special gc method to make the gc initialize=20
memory with a specific pattern to check for non-initialized variables?

How do you compile install the gc? Do you use one of the special=20
makefiles or the configure script? If you use the configure script=20
perhaps send the output (packed) to the mailinglist. Stewart, does it=20
generate a config.h, where we could detect strange configurations?

As Stewart hinter, try to explicitely compile the gc (and oo2c) single=20
threaeded, if multi-threaded is the default.


I do not have Suse 9.0 in reach. I have compiled the oo2c on Sun=20
Solaris, Windows, Mac OS X, and various Debian versions (woody and=20
testing) on x86 and ppc processors and never had a problem. Strange...

--=20
Gru=DF...
        Tim.

Re[2]: [ooc-compiler] Segmentation fault during installation

[vedmed <ve...@in...>]

Hello Jan,

Tuesday, February 10, 2004, 6:03:42 AM, you wrote:

J> At the moment, I think the problem must be be related to my distribution
J> (SuSE 9.0 professional): I just finished trying installation on a 
J> different machine at work that's running the same distribution (without 
J> gc) with exactly the same results and behaviour that I get here at home.

J> Is there anyone using SuSE 9.0 who installed oo2c successfully? Are 
J> there any libs or programs used during installation that might be 
J> missing/corrupt/wrong version in SuSE 9.0?

I have successfully install gc6.3alpha4 and oo2c 2.0.18 on fresh
installed SuSe 9.0
At installation into home directory on SuSe to me it was necessary to
specify a path to libraries at /etc/ld.conf and to execute ldconfig
after installing gc.
Other distribution (Fedora 1) did not demand these actions.
For installation of packages instead of start configure the following
bash script was used

#! /bin/sh
PRF=$HOME/local
export LDFLAGS=-L$PRF/lib
export CFLAGS=-I$PRF/include
export LD_LIBRARY_PATH=$PRF/lib
export PKG_CONFIG_PATH=$PRF/lib/pkgconfig
export CPP="gcc -E -I$PRF/include"
./configure --prefix=$PRF $*

on my computer ~/bin is a symlink to ~/local/bin

-- 
Best regards,
 vedmed                            mailto:ve...@in...

Re: [ooc-compiler] Solved: Segmentation fault during installation

[Jan <juh...@mn...>]

Thanks to the many suggestions in the list, I was able to solve the 
problem today, at least as far as the compiler is concerned (still 
struggling with VO, though). I'm still trying to figure out  what caused 
the fault in the end, but what i did was

- use the most recent gc6.3alpha. I think that the other versions didn't 
install completely on my system, but this one did. Before that, I always 
had to install the includes by hand, dont ask me why.

- I adopted vedmeds suggestion for a script to run configure with all 
the environment vars defined properly. Since I didnt chose any exotic 
places for installation i didnt consider this important earlier, but the 
script did the trick for me.

I'm sorry that i'm not able to narrow things down more precisely, 
remember that i'm still quite new to Linux and oo2c.

Jan


vedmed wrote:
> Hello Jan,
> 
> Tuesday, February 10, 2004, 6:03:42 AM, you wrote:
> 
> J> At the moment, I think the problem must be be related to my distribution
> J> (SuSE 9.0 professional): I just finished trying installation on a 
> J> different machine at work that's running the same distribution (without 
> J> gc) with exactly the same results and behaviour that I get here at home.
> 
> J> Is there anyone using SuSE 9.0 who installed oo2c successfully? Are 
> J> there any libs or programs used during installation that might be 
> J> missing/corrupt/wrong version in SuSE 9.0?
> 
> I have successfully install gc6.3alpha4 and oo2c 2.0.18 on fresh
> installed SuSe 9.0
> At installation into home directory on SuSe to me it was necessary to
> specify a path to libraries at /etc/ld.conf and to execute ldconfig
> after installing gc.
> Other distribution (Fedora 1) did not demand these actions.
> For installation of packages instead of start configure the following
> bash script was used
> 
> #! /bin/sh
> PRF=$HOME/local
> export LDFLAGS=-L$PRF/lib
> export CFLAGS=-I$PRF/include
> export LD_LIBRARY_PATH=$PRF/lib
> export PKG_CONFIG_PATH=$PRF/lib/pkgconfig
> export CPP="gcc -E -I$PRF/include"
> ./configure --prefix=$PRF $*
> 
> on my computer ~/bin is a symlink to ~/local/bin
> 

Re: [ooc-compiler] Solved: Segmentation fault during installation

[Tim T. <ra...@ed...>]

Hello!

> Thanks to the many suggestions in the list, I was able to solve the=20
> problem today, at least as far as the compiler is concerned (still=20
> struggling with VO, though). I'm still trying to figure out  what cause=
d=20
> the fault in the end, but what i did was

If you have problems with VO, tell them :-)

--=20
Gru=DF...
        Tim.

Re: [ooc-compiler] Segmentation fault during installation

[Michael v. A. <Mic...@de...>]

Jan <juh...@mn...> writes:
> [...]
> Hi Michael,
> I tried the solution you suggested. I renamed gc.h and libgc.*, so
> that configure wouldn't use them - the results are the same as
> described in my first post.
> 
> At the moment, I think the problem must be be related to my
> distribution (SuSE 9.0 professional): I just finished trying
> installation on a different machine at work that's running the same
> distribution (without gc) with exactly the same results and behaviour
> that I get here at home.

With gc out of the picture, the next likely candidate is gcc.  I never
had any problems with gcc under Linux/ix86, but I have to admit that I
am still running with sturdy old 2.95.4.  You don't happen to have
such an ancient compiler around?  In any case, twiddling with CFLAGS
is probably a good next step.  Please try

  make distclean
  CFLAGS="-O0 -g" ./configure ...

> Is there anyone using SuSE 9.0 who installed oo2c successfully? Are
> there any libs or programs used during installation that might be
> missing/corrupt/wrong version in SuSE 9.0?

And I would like to know if anyone is running gcc 3.3.x under
Linux/ix86?

-- mva

Re: [ooc-compiler] Segmentation fault during installation

[Tim T. <ra...@ed...>]

Hallo!

> And I would like to know if anyone is running gcc 3.3.x under
> Linux/ix86?

Yes me, using Debian testing. Works. No problems. I havn't tested oo2c=20
2.0.18, but will do now. Perhaps that'll change everything ;-)

tim@edge:~$ gcc --version
gcc (GCC) 3.3.2 (Debian)
Copyright (C) 2003 Free Software Foundation, Inc.
Dies ist freie Software; die Kopierbedingungen stehen in den Quellen. Es
gibt KEINE Garantie; auch nicht f=FCr VERKAUFBARKEIT oder F=DCR SPEZIELLE=
=20
ZWECKE.

--=20
Gru=DF...
        Tim.