On 5/31/07, Felipe Almeida Lessa [EMAIL PROTECTED] wrote:
BTW, how do you usually proceed when finding out why your code said
Segmentation fault.? (should this question move to a new thread?)
$ gdb my_crashing_program
[wait till crush]
[on the gdb command line:]
$ bt
[prints backtrace]
If
Hello =),
I'm puzzled, and maybe someone can help me out. Why does this happens?
$ time ghci -e last $ take 100 $ [1..100]
100
real0m0.673s
user0m0.554s
sys 0m0.024s
$ time ghci -e last $ take 100 $ [1..]
*** Exception: stack overflow
real0m1.305s
user
On Wed, May 30, 2007 at 11:41:55PM -0300, Felipe Almeida Lessa wrote:
Hello =),
I'm puzzled, and maybe someone can help me out. Why does this happens?
$ time ghci -e last $ take 100 $ [1..100]
100
real0m0.673s
user0m0.554s
sys 0m0.024s
$ time ghci -e last $
On 5/30/07, Stefan O'Rear [EMAIL PROTECTED] wrote:
No, because anything you file will be closed immediately as duplicate
of http://hackage.haskell.org/trac/ghc/ticket/1097;
Oh, sorry for not having searched better for this problem on the net.
I spend a lot of time finding out where the stack
On Thu, May 31, 2007 at 12:15:01AM -0300, Felipe Almeida Lessa wrote:
On 5/30/07, Stefan O'Rear [EMAIL PROTECTED] wrote:
No, because anything you file will be closed immediately as duplicate
of http://hackage.haskell.org/trac/ghc/ticket/1097;
Oh, sorry for not having searched better for this
On 5/31/07, Stefan O'Rear [EMAIL PROTECTED] wrote:
You don't need to feel too bad about this:
[snip]
Don't worry, I should have googled anyway =).
BTW, how do you usually proceed when finding out why your code said
Segmentation fault.? (should this question move to a new thread?)
Thanks,
On Thu, May 31, 2007 at 12:34:36AM -0300, Felipe Almeida Lessa wrote:
On 5/31/07, Stefan O'Rear [EMAIL PROTECTED] wrote:
You don't need to feel too bad about this:
[snip]
Don't worry, I should have googled anyway =).
BTW, how do you usually proceed when finding out why your code said
