Re: problem with sablevm-1.1.9 xscale
"Grzegorz B. Prokopski" <[email protected]>
| Newsgroups | gmane.comp.java.vm.sablevm.general |
|---|---|
| Organization | Debian http://www.debian.org - The Free Operating System |
| Message-ID | <[email protected]> |
On Tue, 2005-22-02 at 06:09 +0000, Asutosh Gopinath wrote: > Grzegorz B. Prokopski <gadek <at> sablevm.org> writes: > > > > > On Wed, 2005-16-02 at 11:14 +0000, Asutosh Gopinath wrote: > > > > So there really is a problem. > > Something fishy is going on and I don't (anymore) believe that ie. "real > > life brokenness" is broken. Reading .jar files that are on CLASSPATH > > must not depend on sablevm being compiled in debug mode or not! > > > > if seems there is some problem with -O2 (gcc 3.3.1). i rebuilt with -O1 and -O3 > and in both the cases rxtx problem disappear. but brokeness is still > encountered . The 'brokenness' problem might be just a manifestation of the real problem that does not go away no matter what compiler options you use. You should try to solve one of the visible problems first, it might turn out that it will fix all the others too. Pick which of them (brokeness or assertion failure w/ debugging) is easier to debug and try to find out what is happening. I usually start with the problems that show up in the debug version, as an unoptimized code is much easier to follow, and if an assertion fails, it means the problem is caught "early". You could also try to add some more assertions around the place where things fail, especially if debugging with GDB/DDD is not easily achievable. HTH GBP -- Grzegorz B. Prokopski <[email protected]> SableVM - Free, LGPL'ed Java VM http://sablevm.org Why SableVM ?!? http://sablevm.org/wiki/Features Debian GNU/Linux - the Free OS http://www.debian.org