We are using XPCOM and XULRunner to control the browser control inside Eclipse (which is essentially Firefox embedded inside Eclipse). We are experiencing a crash in xul.dll (on Windows) and libxul.so (on Linux). Java VM produces a crash log with stack trace with addresses in xul.dll. Is it possible to look up these addresses in a pdb file or symbol file to find out which function is causing this crash? Any help in this direction will be greatly help us figure this crash out.
We have built a debug version of xulrunner and xpcom libraries - but crash does not happen with debug build. That is why we have to try to figure out these function calls in the stack trace from a non debug build.