[chromium-dev] Re: chrome always break in debugger when run under XCode

2009-06-10 Thread 鵜飼文敏
Hi,

You should check the code just before logging::LogMessage::~LogMessage().
In this case, you hit DCHECK(!update_in_progress_) in
safe_browing_service.cc at line 466, so that DCHECK breaks here.  Because of
DCHECK, I think SafeBrowsingService::UpdateStarted() expects it never called
when update_in_progress_ is true, but the assumption is failed.

-- 
Fumitoshi Ukai


On Sun, Jun 7, 2009 at 11:48 AM, Nathan Summer 
nathan.charles.sum...@gmail.com wrote:

 Hi,
 I compile chrome and run under XCode.

 But it breaks here, can you please tell me why? And what does BreakDebugger
 do?

 // static

 void DebugUtil::BreakDebugger() {

 #if defined(ARCH_CPU_ARM_FAMILY)

   asm(bkpt 0);

 #else

   asm(int3);

 #endif

 }

 Here is the stack trace:

 #0 0x0058c43f in DebugUtil::BreakDebugger at debug_util_posix.cc:116
 #1 0x005ad984 in logging::LogMessage::~LogMessage at logging.cc:545
 #2 0x0040e751 in SafeBrowsingService::UpdateStarted at
 safe_browsing_service.cc:466
 #3 0x003e7c4a in SafeBrowsingProtocolManager::IssueUpdateRequest at
 protocol_manager.cc:486
 #4 0x003e7cc9 in SafeBrowsingProtocolManager::GetNextUpdate at
 protocol_manager.cc:157
 #5 0x003ed24a in DispatchToMethodSafeBrowsingProtocolManager, void
 (SafeBrowsingProtocolManager::*)() at tuple.h:412
 #6 0x003ed28d in base::BaseTimerSafeBrowsingProtocolManager,
 false::TimerTask::Run at timer.h:160
 #7 0x005b07c3 in MessageLoop::RunTask at message_loop.cc:309
 #8 0x005b0b87 in MessageLoop::DeferOrRunPendingTask at message_loop.cc:317
 #9 0x005b0d0a in MessageLoop::DoDelayedWork at message_loop.cc:450
 #10 0x005bb154 in base::MessagePumpLibevent::Run at
 message_pump_libevent.cc:228
 #11 0x005b18bb in MessageLoop::RunInternal at message_loop.cc:198
 #12 0x005b18d7 in MessageLoop::RunHandler at message_loop.cc:181
 #13 0x005b1962 in MessageLoop::Run at message_loop.cc:155
 #14 0x005f30a9 in base::Thread::ThreadMain at thread.cc:156
 #15 0x005c72c4 in ThreadFunc at platform_thread_posix.cc:26
 #16 0x92129155 in _pthread_start
 #17 0x92129012 in thread_start



 


--~--~-~--~~~---~--~~
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
http://groups.google.com/group/chromium-dev
-~--~~~~--~~--~--~---



[chromium-dev] Re: chrome always break in debugger when run under XCode

2009-06-07 Thread Robert Sesek

Hi Nathan,

I started noticing the same problem this week, too. The class looks
like it's supposed to help developers by attaching a C++ debugger
whenever a critical exception is raised, so they can view the stack
trace and inspect variables. What I think happens is that Chromium
thinks that Xcode's debugger is listening when it really isn't, and it
crashes.

When you run Chromium.app via Run -- Debug, you can get over the
breakpoint by pressing the continue button, or typing 'c' in gdb. But
if you run the application via Run -- Run or by opening it in Finder,
the breakpoint turns fatal and terminates the app.

I've just commented out the two asm() lines in my tree because I find
the breakpoints more annoying than helpful. I think it would be better
if DebugUtil's features were enabled with a build or runtime flag,
rather than having to resort to commenting it out.

- Robert Sesek

On Jun 6, 10:48 pm, Nathan Summer nathan.charles.sum...@gmail.com
wrote:
 Hi,
 I compile chrome and run under XCode.

 But it breaks here, can you please tell me why? And what does BreakDebugger
 do?

 // static

 void DebugUtil::BreakDebugger() {

 #if defined(ARCH_CPU_ARM_FAMILY)

   asm(bkpt 0);

 #else

   asm(int3);

 #endif

 }

 Here is the stack trace:

 #0 0x0058c43f in DebugUtil::BreakDebugger at debug_util_posix.cc:116
 #1 0x005ad984 in logging::LogMessage::~LogMessage at logging.cc:545
 #2 0x0040e751 in SafeBrowsingService::UpdateStarted at
 safe_browsing_service.cc:466
 #3 0x003e7c4a in SafeBrowsingProtocolManager::IssueUpdateRequest at
 protocol_manager.cc:486
 #4 0x003e7cc9 in SafeBrowsingProtocolManager::GetNextUpdate at
 protocol_manager.cc:157
 #5 0x003ed24a in DispatchToMethodSafeBrowsingProtocolManager, void
 (SafeBrowsingProtocolManager::*)() at tuple.h:412
 #6 0x003ed28d in base::BaseTimerSafeBrowsingProtocolManager,
 false::TimerTask::Run at timer.h:160
 #7 0x005b07c3 in MessageLoop::RunTask at message_loop.cc:309
 #8 0x005b0b87 in MessageLoop::DeferOrRunPendingTask at message_loop.cc:317
 #9 0x005b0d0a in MessageLoop::DoDelayedWork at message_loop.cc:450
 #10 0x005bb154 in base::MessagePumpLibevent::Run at
 message_pump_libevent.cc:228
 #11 0x005b18bb in MessageLoop::RunInternal at message_loop.cc:198
 #12 0x005b18d7 in MessageLoop::RunHandler at message_loop.cc:181
 #13 0x005b1962 in MessageLoop::Run at message_loop.cc:155
 #14 0x005f30a9 in base::Thread::ThreadMain at thread.cc:156
 #15 0x005c72c4 in ThreadFunc at platform_thread_posix.cc:26
 #16 0x92129155 in _pthread_start
 #17 0x92129012 in thread_start
--~--~-~--~~~---~--~~
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
http://groups.google.com/group/chromium-dev
-~--~~~~--~~--~--~---