http://code.google.com/p/chromium/wiki/LinuxDebugging has a section on debugging renderers. I'd try the --single-process trick I just added to it. (Despite the page having Linux in the title the gdb tips mostly apply to a Mac as well.)
On Thu, Aug 6, 2009 at 9:43 PM, n179911<[email protected]> wrote: > > Hi, > > When I load a page on chromium that I run on debugger,I get 'Aw, Snap! > Something went wrong while displaying this webpage.' error. > > And I see this in the console: > WebCore::FrameView::paintContents(WebCore::GraphicsContext*, const > WebCore::IntRect&)) > LEAK: 1899 RenderObject > LEAK: 1 Page > LEAK: 19 Frame > LEAK: 1 SubresourceLoader > LEAK: 141 CachedResource > LEAK: 4197 WebCoreNode > [1487:2067:12214450218929:ERROR:../chrome/common/temp_scaffolding_stubs.h(75)] > Not implemented reached in bool > printing::PrintViewManager::OnRenderViewGone(RenderViewHost*) > > My question is how can i debug problem like this? Is there a stack > trace or core dump for situation like this? > > Thank you. > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
