On Wed, 06 Jul 2005 18:10:26 +0100, Gary Benson wrote: > There's no generic way, but if you have already compiled a solib > yourself then it won't recreate it. This allows you to compile it > with -O0 instead of -O2, for example, which has worked for every gcj > bug I've seen so far. By the way - if you compile with -O0, find-debuginfo.sh fails to find the source code, so you end up with missing source code in the -debuginfo package. See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161722 where I've supplied a fix. This may be a moot point at the moment however, because some Java -debuginfo packages don't have any source code anyway, for another reason - see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=153247 Obviously both are low-priority bugs at best, because you can just get the source code from the corresponding .src.rpm, rpmbuild -bp foo.spec to apply any patches, and then optionally shove it where the debugger can find it, which should work in 99% of cases, but I thought I'd mention them anyway. -- Robin
