home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Club Amiga de Montreal - CAM
/
CAM_CD_1.iso
/
files
/
545a.lha
/
PowerVisor_v1.0
/
pv.bugs
< prev
next >
Wrap
Text File
|
1991-09-06
|
4KB
|
73 lines
Bugs
mmu 'mmutree' does not support indirect pages and 8 byte
descriptors
'mmutree' does not support FC trees (function codes)
input handler key repetition for scrolling in a logical window does
not work good in AmigaDOS 1.3
fonts if logical windows are dragged too small with a big font,
a crash may happen
stringgadget font of stringgadget should be fixed to topaz
signals maybe we should share some signals, we have only five
signals left
symbols I think something is wrong with symbols because some
people reported strange behaviour. I can't find the
bug, so maybe it was caused by something else. Maybe
the bug is even solved :-)
loadfd I don't think I handle multiple #bias statements completely
correctly (in most cases it will work). I need to test
this command
locks Break... is not printed when we interrupt the lock listing
This harmless bug is a replacement for a memory loosing
bug. I like this bug better :-)
ColRow If 'colrow' failes there is no safe way to get back. So
out of memory conditions with 'colrow' are rather fatal
Stack overflow There seem to be some problems with 'killing' a task
that has crashed because of a stack overflow
Things that could be better and maybe should be supported
disp 1a should give an error
trace u PowerVisor may disturb other programs if you set your
breakpoint in shared memory
free The Free function should check if the memory you
try to free is OK
trace Tracing is very hazardous for multitasking. You can
scarcely move your mouse
crashes There are still some guru's PowerVisor does not trap
crash trapping Address Errors are not recoverable
fonts We should not permit proportional fonts
search/copy/fill
These routines are very sensitive to bad arguments
(negative for example)
Overflows Powervisor does not always check for overflow (especially
strings)
Future enhancements
Workbench Support for workbench startup
load Load must have an extra argument : offset to start loading
loadtags When you save tags containing pointers to structures, these
pointers will later point to nowhere. This should be solved
somehow
customize I plan to make a seperate file containing all command
strings, function strings and some other strings. That way
the user will be able to customize PowerVisor by changing
this file. This file will not be resident in memory.
PowerVisor will build internal data structures using this
file
pvcall Instead of only one command for each installable post or
pre command I plan to incorporate a list system (see the
TheWizardCorner file for the 'pvcall' command)
mmu I have been thinking about a very powerful system to
use the mmu for protecting memory. PowerVisor could be
protected from other programs and some extra commands
could be provided to read or write protect regions
of memory
stack checking I plan a more useful stackchecking for one specific task.
This checker would use the timer device for faster
response. This checker would also include an indicator
for the maximum stack use for that program