date:20100913

Re: web-based Cocoa dev docs inaccessible

2010-09-13 Thread Andy Lee

On Sep 12, 2010, at 6:32 PM, Jeffrey Oleander wrote:
> Normally, I'd file an on-line criticism of the docs, but I can't get there, 
> and this is the closest means I have to doing so.

This list isn't an official channel for bug reports, so filing a Radar might 
actually be closer:

> 
> I was trying to look up something about NSAttributedStrings
> and found that the usual link led me to a page that no longer
> has a search box, links to docs, etc.
> 
> My BookMark has the URL:
> http://developer.apple.com/mac/library/navigation/index.html

This link works for me.  I get a page titled "Mac OS X Reference Library", with 
a search box and other stuff I expect.  Maybe you ran into a temporary glitch 
on Apple's servers?

> 
> but it took me here, so apparently there's a redirect:
> http://developer.apple.com/library/mac/#navigation/index.html

It works the other way for me: the "#navigation" link redirects to the 
"navigation" link.

> 
> and by successive trimming (first of "index.html" and then of everything from 
> the pound sign right) to try to get to something that works I tried this:
> http://developer.apple.com/library/mac/
> 
> When I trim off more, removing the "mac/" it takes me to 
> http://developer.apple.com/resources/
> Trying links from there, merely takes me back to the same garbage.

The resources link works for me.

What browser are you using?  Do you have any plugins or extensions installed 
that might be mucking with URLs or CSS?  What if you try a different browser?  
What if you try clearing your cache?

--Andy

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Unix Signals Delivered from Quitting Cocoa Apps?

2010-09-13 Thread aaron smith

Hey all, quick question.

I'm working on a test to catch when an application crashes, and launch
another executable (eventually crash reporter).

I'm exhibiting strange behavior - whenever I quit the application
normally, the information I'm getting back about what happened and why
it stopped is always a signal, but the signal is never the same.

So a couple questions:

-Where can I find all of the signal definitions? I've found up to
about 50 of them, but I'm getting signals in the hundreds.
-Would you be willing to skim this code real quick?
(http://pastebin.org/859983). It's pretty short. The focus is the
main() function.

There are a couple printf's in there just so I could figure out which
signals are being reported. I'm getting all kinds. Here's a couple of
session outputs.

--
error: Interrupted system call
waited: 7095
signal: 55
--
error: Interrupted system call
waited: 7136
signal: 96
--
error: Interrupted system call
waited: 7151
signal: 111

I get these from quitting the application normally (cmd+q) or going to
the menu>quit option.

Since I'm not able to find where some of these signals are defined I'm
not sure what they are.

Alternatively, I found a list of signals that come directly from the
kernel and are sent to processes:
http://www.mugginsoft.com/content/how-crash-cocoa-app-testing-purposes-abnormal-termination
http://www.opensource.apple.com/source/xnu/xnu-1228.3.13/bsd/uxkern/ux_exception.c?f=text
would it be valid to check against those and ignore the rest?

46 matches

Mail list logo