• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: crashing web browser with openURL call
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: crashing web browser with openURL call


  • Subject: Re: crashing web browser with openURL call
  • From: Greg Guerin <email@hidden>
  • Date: Sat, 6 Jun 2009 10:43:24 -0700

iseecolors wrote:

What I am doing is a single sign on to an web service. I send the URL (with cert and nounce) to the server and get back a re-direct to the actual page, which does start to load. I see all of this take place. Than before the page finishes loading, the browser quits. The interesting note is that what little the log shows is that Debugger() is called just before the browsers quit. It seems odd that both browsers would call Debugger() when loading the same page, but only when the browser didn't already have a page open - suggestion some common code is actually calling Debugger().


Set a breakpoint on the symbol "Debugger". Any code that intentionally calls Debugger() is almost certainly trying to make an orderly call into the debugger. That apparently isn't working, so give it a helping hand by starting the debugger before the app gets to that point.

You can attach the debugger to any running process. I suggest doing this before the redirect, so you can set the breakpoint.


FWIW, my interpretation of the console output:

6/5/09 2:11:34 PM [0x0-0xa70a7].com.apple.Safari[3281] Debugger() was called!
6/5/09 2:11:34 PM com.apple.launchd[132] ([0x0-0xa70a7].com.apple.Safari[3281]) Exited abnormally: Interrupt


First line: Safari (process id 3281) is telling you that Debugger() was called.

Second line: launchd (whose process id is 132), and which is almost certainly the parent process of Safari on Leopard, is telling you that its Safari child-process has exited with a status code that indicates the child received a SIGINT (interrupt) signal. My guess is that Debugger() does this, i.e. calls exit() with 128+SIGINT, which is the traditional way to tell a parent process that a child is terminating due to an abnormal condition.

  -- GG

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Prev by Date: RE: A couple questions about graphics
  • Next by Date: Re: Backtabbing into an NSTableView
  • Previous by thread: Re: crashing web browser with openURL call
  • Next by thread: understanding problem; creation of instances of objects; xCode vs. Menu Builder
  • Index(es):
    • Date
    • Thread