Re: SableVM on ARM Zaurus
"Grzegorz B. Prokopski" <[email protected]>
| Newsgroups | gmane.comp.java.vm.sablevm.general |
|---|---|
| Organization | SableVM - LGPL'ed Free Java VM http://sablevm.org |
| Message-ID | <[email protected]> |
On Wed, 2005-12-01 at 16:28 -0500, Chris Pickett wrote: > I have recently been getting segfaults with --enable-debugging-features > and --with-profiling=yes turned on, but it just says the function name > (e.g. _svmf_interpreter ()), without line number information. Is there Are you getting these segfaults even --without-profiling ? I guess not. It might be interaction between gcc's profiling and inlined engine. Try using direct and with profiling. If that solves the problem, I guess we should make direct the default with profiling. > something extra I need to do, such as use '-g', or do you guys get line > number info in SableVM with segfaults like this? I don't think gcc's profiling was designed to give us stack traces on segfaults, but maybe there is some method. I assume that you _do_ get the full profile output at the end, when there was no segfault? Cheers, Grzegorz B. Prokopski -- 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