Re: [racket-users] a little bug

On Fri, Feb 28, 2020 at 07:11:02AM -0600, Robby Findler wrote: > Oh, sorry-- I misunderstood. > > In v7.5, there will be, in some cases, a source location after you > dismiss that dialog. In the pre-release builds, that's been improved > somewhat and source location information is more reliably

Re: [racket-users] a little bug

Oh, sorry-- I misunderstood. In v7.5, there will be, in some cases, a source location after you dismiss that dialog. In the pre-release builds, that's been improved somewhat and source location information is more reliably available. That said, there are limitations and it isn't always available.

Re: [racket-users] a little bug

On Fri, Feb 28, 2020 at 06:02:31AM -0600, Robby Findler wrote: > I agree that would be great. In the meantime, the Run button does a better > job with error reporting in various ways, including this one so hopefully > you can try that? That's what I was using. There was a popup message that

Re: [racket-users] a little bug

I agree that would be great. In the meantime, the Run button does a better job with error reporting in various ways, including this one so hopefully you can try that? Robby On Fri, Feb 28, 2020 at 5:45 AM Hendrik Boom wrote: > > When Racket detects the out-of-memory condition during

Re: [racket-users] a little bug

When Racket detects the out-of-memory condition during "background processing", it would be useful i the out-of-memory message were to point out which particular piece of source text it was having trouble with. Just the line number where the expression started that the REPL was having

Re: [racket-users] a little bug

Thanks for the explanation. I appreciate it. On 2/5/2016 1:55 PM, Robby Findler wrote: In general, DrRacket does not promise to avoid this situation. Let me explain a little bit. This program is effectively equivalent to this one: #lang racket/base (define (run l) (run (cons 'x l))) (run

Re: [racket-users] a little bug

Setting the limit lower helped. Thanks. I did not see that message about Background Expansion Terminated before. Now I do. Jon On 2/5/2016 6:55 AM, Robby Findler wrote: It took a while for mine for the custodian limit to be reached and for the expansion to run out of memory. It may be that

Re: [racket-users] a little bug

Actually you don't even have to run the program. With memory limit set to 1024, just open a file containing the expression and wait. After a minute or two DrRacket puts up a MSVC runtime error dialog. On 2/5/2016 9:39 AM, jon stenerson wrote: Setting the limit lower helped. Thanks. I did not

Re: [racket-users] a little bug

Sorry we can't do better. And it is really amazing how I actually think so anthropomorphically about these things. :) That really was a literal brain dump. Robby On Fri, Feb 5, 2016 at 3:53 PM, jon stenerson wrote: > Thanks for the explanation. I appreciate it. > > >

Re: [racket-users] a little bug

In general, DrRacket does not promise to avoid this situation. Let me explain a little bit. This program is effectively equivalent to this one: #lang racket/base (define (run l) (run (cons 'x l))) (run '()) (but running at compile time, which is why things happen automatically, but lets leave

Re: [racket-users] a little bug

It took a while for mine for the custodian limit to be reached and for the expansion to run out of memory. It may be that the threshhold for the memory use is too high on some systems. Maybe the right thing is to set the default a bit lower? Jon: if you open the "Racket" menu you should see a

Re: [racket-users] a little bug

When I run this, I see a message at the bottom of the DrRacket window (in red): Background expansion terminated abnormally (out of memory) do you see this message? Robby On Thu, Feb 4, 2016 at 10:29 PM, jon stenerson wrote: > > #lang racket > (let ((x 1)) >

Re: [racket-users] a little bug

On 02/05/2016 08:01 AM, Robby Findler wrote: > When I run this, I see a message at the bottom of the DrRacket window (in > red): > > Background expansion terminated abnormally (out of memory) > > do you see this message? I tried too, and it stops fine with the same message as Robby. No

Re: [racket-users] a little bug

On my system it behaves almost exactly as described by Jon (6.3, windows). The one difference is that DrRacket hasn't crashed yet, but the Task manager reports one processor at 100% and memory use slowly growing. Currently is at 7.5 GB. On Fri, Feb 5, 2016 at 2:29 PM, Anthony Carrico

Re: [racket-users] a little bug

lol. Don't be sorry. Speaking of anthropomorphization, I really love Dr Racket and hope I didn't hurt his feelings (Or is Dr Racket a she?). I employ his services whenever I can. I don't mean to be a whiner; he deserves better than that! Jon On 2/5/2016 3:44 PM, Robby Findler wrote: Sorry

[racket-users] a little bug

#lang racket (let ((x 1)) (letrec-syntax ((m (lambda (t) (syntax (m) (m))) When I run this in DrRacket 6.3 on Win 10 it starts looping. I hit the stop button. The interaction window says "user break" and is ready for another command. However, the windows task manager shows