Hello You know that drlvm was donated by Intel and there was some period of time while drlvm was developed internally. We had an internal bugzilla server to track the issues. In an effort to move all development to the open this internal bugzilla will be closed.
The database is quite big and contains a lot of valuable information including still open bugs. There are many of them which are not exactly bug reports, but requests for enhancements or limitation problems. These small issues didn't make it to README because they are mostly minor and low priority, but it is better to use information which we have already than rediscover these problems again. So not to create a lot of garbage in JIRA like problem requests without patches I think it is better to create something like a TODO list for drlvm. Not exactly bugs, but more like known limitations list. To give you an example, vm/vmcore/src/init/properties.cpp contains a #define MAX_PROP_LINE 5120 which is a maximum property length specified in vm.properties file. I am not even sure if this file still used, probably not, but a buffer length limitation is still a bad thing. I think a good place for such list would be on wiki. I am going to create a page for it so that everyone who has open bugs inside of Intel could add a line or two describing a problem recorded in bugzilla. I have 3 like these filed myself including the one I gave as an example. I don't know the number of such bugs overall, maybe it is not so big. But before creating JIRAs for them I think it is better to collect a list on wiki. What do you think? -- Gregory Shimansky, Intel Middleware Products Division --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
