I should have followed your suggestion to to rebuild gcc for Solaris 2.7
right away.  After rebuilding gcc, the source build and install of 5.02.2
had no problems.
I am really sorry having wasted your time with something I had control
over myself.  While I am curious what difference in the assembly files
made the ghc-split perl script fail with a bus error, there here is probably
not much value in pursuing this. Let me know otherwise and I will try
to capture the intermediate files for analysis.

Thanks again,
Martin

Martin Dorr wrote:

> Simon Marlow wrote:
>
> > > $ gcc -v
> > > Reading specs from .../gcc-lib/sparc-sun-solaris2.5.1/2.95.2/specs
> > > gcc version 2.95.2 19991024 (release)
> >
> > I don't know if this is relevant, but the above gcc looks like it was
> > built on Solaris 2.5, but you're on a 2.7 system.  Perhaps rebuild gcc
> > to be on the safe side?
>
> I wish I could, but I am tied in using a much larger set of tools with
> many other people running Solaris 2.5.1, 2.7, and 2.8.   So far we have
> not found any problems running those 2.5.1 compiled tools on any of
> our systems.  But, as you said, there is always a chance and I will
> keep it in mind.
>
> > Just so I'm clear on what we're actually examining here:  this is the
> > 5.02.2 sources built using the 5.02.2 binary distribution, right?
>
> Yes
>
> > You're not using 5.02.1 to build with?  (it'll be easier to track down
> > if we're bootstrapping 5.02.2 with itself).
>
> I ran into the problem using 5.02.1 binaries, upgrading to 5.02.2 did
> not help.
>
> > Could you try changing the heap size when running the offending
> > compilation and see if the core dump goes away?  If it doesn't vary with
> > the heap size, then it is probably much easier to track down because it
> > won't be GC-related.
>
> I grabed the failing invocation and added +RTS -H10m, and then -H20m.
> All invocations fail the same way.
>
> > > I tried looking at the core dump with ddd, but it got an
> > > internal bus error
> > > while loading the the core file.
> >
> > gdb shouldn't crash (I hope).  If it does, we're up the creek.
>
> Using gdb, I found that the core was from a perl invocation.  Using -v3
> I found ghc-split to dump core.
>
>     :
> *** Splitter
> /home/dorr/func/haskell/sources/ghc-5.02.2/ghc/driver/split/ghc-split 
>/tmp/ghc21821.split_s /tmp/ghc21821.split
> /tmp/ghc21821.split
> Bus Error - core dumped
>     :
>
> How can I preserve the tmp files, so I can debug the perl run?  I don't
> know anything about what split is supposed to achieve.  Where should
> I read up on this?
>
> Martin

_______________________________________________
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to