Re: MacOS X / PowerPC

2006-07-07 Thread Simon Marlow

Gregory Wright wrote:


I followed the instruction in DebuggingGhcCrashes, and the
instructions in the ghc commentary for building an rts with debugging
and symbols.  (Please let me know if there are any mistakes in
these instructions that you know of!)

The crash seems to always happen eventually, but I do not have
a simple case that reproduces it quickly.  Gdb's traceback doesn't  give 
anything

immediately useful, so I assume that the crash is in haskell code, not
in C.  The not-always-reproducible nature of the bug suggests
deferencing a pointer into uninitialized memory.

Both 6.4.2 and HEAD show the problem on OS X.   It can be avoided by
disabling the threaded rts, but that is not acceptable solution.


This is a good datapoint, because it probably rules out much of the 
threaded RTS code in the RTS itself, which has changed significantly 
between 6.4.x and HEAD.



If I am to take a few deep breaths and dive back into the problem,
which branch should I use, 6.4.x or HEAD?


No preference, since it's probably the same bug in both.  Use whatever's 
easiest for you.


Cheers,
Simon
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


Re: MacOS X / PowerPC

2006-07-07 Thread Gregory Wright


Hi Simon,

On Jul 7, 2006, at 4:26 AM, Simon Marlow wrote:


Gregory Wright wrote:


I followed the instruction in DebuggingGhcCrashes, and the
instructions in the ghc commentary for building an rts with debugging
and symbols.  (Please let me know if there are any mistakes in
these instructions that you know of!)
The crash seems to always happen eventually, but I do not have
a simple case that reproduces it quickly.  Gdb's traceback  
doesn't  give anything
immediately useful, so I assume that the crash is in haskell code,  
not

in C.  The not-always-reproducible nature of the bug suggests
deferencing a pointer into uninitialized memory.
Both 6.4.2 and HEAD show the problem on OS X.   It can be avoided by
disabling the threaded rts, but that is not acceptable solution.


This is a good datapoint, because it probably rules out much of the  
threaded RTS code in the RTS itself, which has changed  
significantly between 6.4.x and HEAD.




A quick question: does the darcs repository have go back to 6.4.1?
(The place to start looking a diff of the RTS from 6.4.1, which worked,
and 6.4.2 or HEAD, which doesn't).


If I am to take a few deep breaths and dive back into the problem,
which branch should I use, 6.4.x or HEAD?


No preference, since it's probably the same bug in both.  Use  
whatever's easiest for you.




I'll work with HEAD.

Best Wishes,
Greg



Cheers,
Simon


___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


Re: MacOS X / PowerPC

2006-07-07 Thread Simon Marlow

Gregory Wright wrote:


A quick question: does the darcs repository have go back to 6.4.1?
(The place to start looking a diff of the RTS from 6.4.1, which worked,
and 6.4.2 or HEAD, which doesn't).


No, 6.4.x is in CVS only.  ghc-6-4-branch of CVS, to be precise.

Cheers,
Simon
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


Re: MacOS X / PowerPC

2006-07-06 Thread Simon Marlow

Gregory Wright wrote:


I submitted a patch for ticket #766 this afternoon.


Thanks, now comitted and merged.


I've banged my head on ticket #751, building with debugging symbols
and running under gdb, but have yet to get any useful information that
would pin down the bug.


Does http://hackage.haskell.org/trac/ghc/wiki/DebuggingGhcCrashes help 
at all?


Cheers,
Simon
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


Re: MacOS X / PowerPC

2006-07-06 Thread Gregory Wright


Hi Simon,

I followed the instruction in DebuggingGhcCrashes, and the
instructions in the ghc commentary for building an rts with debugging
and symbols.  (Please let me know if there are any mistakes in
these instructions that you know of!)

The crash seems to always happen eventually, but I do not have
a simple case that reproduces it quickly.  Gdb's traceback doesn't  
give anything

immediately useful, so I assume that the crash is in haskell code, not
in C.  The not-always-reproducible nature of the bug suggests
deferencing a pointer into uninitialized memory.

Both 6.4.2 and HEAD show the problem on OS X.   It can be avoided by
disabling the threaded rts, but that is not acceptable solution.

If I am to take a few deep breaths and dive back into the problem,
which branch should I use, 6.4.x or HEAD?

Best Wishes,
Greg


On Jul 6, 2006, at 8:13 AM, Simon Marlow wrote:


Gregory Wright wrote:


I submitted a patch for ticket #766 this afternoon.


Thanks, now comitted and merged.


I've banged my head on ticket #751, building with debugging symbols
and running under gdb, but have yet to get any useful information  
that

would pin down the bug.


Does http://hackage.haskell.org/trac/ghc/wiki/DebuggingGhcCrashes  
help at all?


Cheers,
Simon
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


MacOS X / PowerPC

2006-07-05 Thread Simon Marlow
Hi Folks,

As you may know, support on MacOS X/PowerPC hardware has been lacking a
bit recently: there are outstanding showstoppers with 6.4.2.  Our Mac
hero Wolfgang Thaller has been busy, and hasn't had time to look into
the problems or package 6.4.2 for MacOS X (at least I assume he's busy,
that's the last I heard, but he didn't respond to my latest ping).

So the mantle of powerpc-apple-darwin maintainer is probably up for
grabs.  6.4.3 is held up because of this (but not just because of this).
Can anyone help out?

Relevant bugs:

  http://hackage.haskell.org/trac/ghc/ticket/751
  http://hackage.haskell.org/trac/ghc/ticket/766

and Wolfgang, if you're listening, we miss you :-)

Cheers,
Simon
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


Re: MacOS X / PowerPC

2006-07-05 Thread Wolfgang Thaller

X (at least I assume he's busy,
that's the last I heard, but he didn't respond to my latest ping).


Oops, sorry about that. Yes, I'm quite busy, trying to get a degree  
here.

Proper Mac OS X support will resume on September 1st :-).


So the mantle of powerpc-apple-darwin maintainer is probably up for
grabs.  6.4.3 is held up because of this (but not just because of  
this).

Can anyone help out?


GHC/Mac OS X users, I know you are out there, and I know that many of  
you are capable of building GHC and running gdb on it! Please step  
forward now!


Similar things to be said for the Mac OS X/Intel port, which is  
basically there, but which I will not finish before I both a)  
finish my degree and b) get an actual Intel based Mac of my own. So  
another job opening there.


Cheers,

Wolfgang

___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


Re: MacOS X / PowerPC

2006-07-05 Thread Gregory Wright


Simon,

I submitted a patch for ticket #766 this afternoon.

I've banged my head on ticket #751, building with debugging symbols
and running under gdb, but have yet to get any useful information that
would pin down the bug.

Best,
Greg


On Jul 5, 2006, at 10:47 AM, Simon Marlow wrote:


Hi Folks,

As you may know, support on MacOS X/PowerPC hardware has been  
lacking a

bit recently: there are outstanding showstoppers with 6.4.2.  Our Mac
hero Wolfgang Thaller has been busy, and hasn't had time to look into
the problems or package 6.4.2 for MacOS X (at least I assume he's  
busy,

that's the last I heard, but he didn't respond to my latest ping).

So the mantle of powerpc-apple-darwin maintainer is probably up for
grabs.  6.4.3 is held up because of this (but not just because of  
this).

Can anyone help out?

Relevant bugs:

  http://hackage.haskell.org/trac/ghc/ticket/751
  http://hackage.haskell.org/trac/ghc/ticket/766

and Wolfgang, if you're listening, we miss you :-)

Cheers,
Simon
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users