samth / test-bugs

2 stars 0 forks source link

profiler error #93

Closed racket-bug-submit closed 12 years ago

racket-bug-submit commented 12 years ago
Originally submitted on: Thu Apr 03 16:50:00 -0500 2003
(I can't seem to get the form from the Help Desk to go through, so I'm sending this via bugs.plt-scheme.)

When running programs with the profiler, particularly with SchemeUnit, the profiler seems to be finding points of the program that have not been set up in the profiler table, and it's raising an error: "hash-table-get: no value found for key: profile-pointXXX" (where XXX is some number).

I first ran across this bug running a long program at work with the profiler on, *not* using SchemeUnit. It crashed partway through the program with a similar error. But since I can't send you proprietary code from work (sorry about that), I can at least reproduce the problem (if it is the same problem) using SchemeUnit.
Steps to Reproduce:
Install SchemeUnit (http://schematics.sourceforge.net). Make a file with the following contents:

;; ------------------------------------------
(require (lib "test.ss" "schemeunit")
         (lib "text-ui.ss" "schemeunit"))

(define my-tests
  (make-test-suite
   "Tests for something.scm"

   (make-test-case
    "Test that succeeds"
    (assert = 2 2))

   (make-test-case
    "I fail.. heh-heh"
    (assert = 2 3))

   )
)

(test/text-ui my-tests)
;; ------------------------------------------

Turn on profiling in the current language. Then click the "Execute" button. I get an error saying "hash-table-get: no value found for key: profile-point501".

Details: I'm using v203 in Windows 2000 Professional. My language level is "Textual (MzScheme, includes R5RS" with the profiling turned on.

Let me know if this doesn't give you enough info and I'll see if I can help figure out how to reproduce it.
Release:

203

Environment:

windows-2000

This bug was converted from Gnats bug 6191.

[anon-submit dherman AT ccs.neu.edu]

racket-bug-submit commented 12 years ago
On Thu, 3 Apr 2003 17:52:23 -0500 (EST), steck@ccs.neu.edu wrote:
dherman@ccs.neu.edu wrote:
> When running programs with the profiler, particularly with SchemeUnit, the profiler seems to be finding points of the program that have not been set up in the profiler table, and it's raising an error: "hash-table-get: no value found for key: profile-pointXXX" (where XXX is some number).

Aha!

PR 6146 reports similar behavior when MysterX COM event handlers
are invoked when profiling is enabled.  I'd thought it was 
particular to MysterX, but this PR suggests otherwise.

-- Paul
racket-bug-submit commented 12 years ago
On Thu, 3 Apr 2003 17:54:57 -0500 (EST), steck@ccs.neu.edu wrote:
John Clements wrote:
> This one is probably my bug. I tried to infer the interaction between 
> the annotater and the profiler based on the existing code, but I'd 
> guess that I missed the mark.

Could that lapse also be responsible for PR 6146?

Is the annotator always used when profiling is enabled?

-- Paul
racket-bug-submit commented 12 years ago
On Thu, 3 Apr 2003 21:13:33 -0600, robby@cs.uchicago.edu wrote:
At Thu, 3 Apr 2003 17:54:57 -0500 (EST), Paul Steckler wrote:
> Is the annotator always used when profiling is enabled?

Yes. That's how it is implemented.

Robby
racket-bug-submit commented 12 years ago
On Sun, 28 Mar 2004 23:27:26 -0500, eli assigned this bug to nobody
racket-bug-submit commented 12 years ago
On Mon, 05 Apr 2004 00:08:27 -0400, eli assigned this bug to eli
racket-bug-submit commented 12 years ago
On Mon, 05 Apr 2004 00:08:27 -0400, eli marked this bug as feedback and wrote:

Again, can you check whether this is still a problem?

racket-bug-submit commented 12 years ago
On Tue, 06 Apr 2004 09:44:51 -0400, dherman@ccs.neu.edu wrote:
Seems to be fixed, or at least I can't reproduce the bug anymore. Thanks,

Dave

eli@plt-scheme.org wrote:
> Responsible changed from "nobody" to "eli" by eli at Mon, 05 Apr 2004 00:08:27 -0400
> Reason>>> Replying
> 
> State changed from "open" to "feedback" by eli at Mon, 05 Apr 2004 00:08:27 -0400
> Reason>>> Again, can you check whether this is still a problem?
> 
> 
> View:
>   http://bugs.plt-scheme.org/query/?cmd=view+audit-trail&pr=6191
>