[comp.os.msdos.programmer] Turbo Profiler bugs reported to Borland

routley@tle.enet.dec.com (10/30/90)

I have submitted the following Turbo Profiler bug report to Borland.

Kevin Routley - Digital Equipment Corporation
routley@tle.enet.dec.com

          Product: Turbo Profiler
          Version: 1.00
          OS: MS-DOS V3.2


          1. Difficulty Aborting Print to Non-existant Printer

             When (accidentally) trying to print to a non-
             existant printer, it is extremely difficult to abort
             the print operation.

             Turbo Profiler will display a message box "Error
             in device, re-try (Y/N)?". I hit N, and Turbo Pro-
             filer appeared to try again, and then displayed
             the same message box. I continued to hit the N key,
             but the Profiler would continue to try and access
             the printer and then display the message box. Af-
             ter a while, it seemed to stop trying to access the
             printer (no pause between message boxes) but con-
             tinued to display the message box. Eventually, the
             print operation stops.

             It appeared that Turbo Profiler was attempting to
             access the non-existant printer for each line of the
             report. The print operation should be aborted when
             the user responds "N" to the re-try message box. The
             user should also have some means of aborting a print
             operation even if the printer is hooked up.

          2. Error in Printing Time per Call statistics to disk

             The second time a Time per Call statistics re-
             port was printed to disk, the area names were not
             printed. The first time the report is printed, the
             report is fine, but not the second.

          3. Inaccuracy in Time per Call display

             The number of asterisks displayed is inaccurate.

             In my program, the highest time per call value was
             _main with 0.90168 seconds per call. The second
             highest was _create, with 0.37921 seconds per call.
             The profile display showed six asterisk for _main,
             and 19 asterisks for _create. _main should have had
             three times as many asterisks as _create.

          4. Statistics Storage Inefficient

             When trying to save statistics to disk, I ran out of
             space after writing seven megabytes of statistics to
             the disk. I would suggest a more efficient storage
             mechanism for statistics information.

          5. Selected Area not Preserved

             The selected area in the Profile window is not
             preserved when the area is in the runtime library.

             Hit the RETURN key in the Profile window to see the
             source associated with the selected area, with the
             area being in the runtime library (e.g. printf) so
             that the CPU window appears. If you then use F6 to
             cycle through the windows, the selected area has
             been changed when you cycle back to the Profile
             window.

             If the originally selected area was in the user
             program, the selection is preserved after cycling
             through windows.

          6. Additional Sort Requested

             When displaying Both Time and Count statistics, I
             would like to be able to sort by count instead of by
             time (e.g. highest count first).

v056ped5@ubvmsd.cc.buffalo.edu (Brian M McNamara) (10/30/90)

In article <16799@shlump.nac.dec.com>, routley@tle.enet.dec.com writes...
>I have submitted the following Turbo Profiler bug report to Borland.
>          1. Difficulty Aborting Print to Non-existant Printer
>             When (accidentally) trying to print to a non-
>             existant printer, it is extremely difficult to abort
>             the print operation.
> 
	[...lots deleted...]

This is a problem I have noticed with many programs. It appears to be
more of a DOS problem in the way that the computer interprets the
command to print in relation to the (abort,ignore,retry) thing. I 
can't remember how many times I have lost programming work, word 
processing work, even game progress, to this problem which only can
be solved by rebooting.

I have also seen this problem occur with some programs when trying to access
a non-existent or not ready drive.

Does anyone have any suggestions?

Brian