• 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: Xcode 3.0 help issues
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 3.0 help issues


  • Subject: Re: Xcode 3.0 help issues
  • From: Ronald Hayden <email@hidden>
  • Date: Mon, 7 Jul 2008 09:17:01 -0700

The general problem is known, so there's no need to file a bug if you don't have extra information to provide.

 -- Ron

On Jul 7, 2008, at 6:18 AM, arri wrote:

Great!

Just in case anyone else runs into this issue:
Removing that file ( docSet.dsidx-journal ) solved the problem for me.

Ronald, i haven't tried to see how to reproduce the problem, and i
suspect this could be a time-consuming hobby.
Is a bug-report still desired, or is the issue solved in current
(doc-set) updates?


gr arri

On Wed, Mar 26, 2008 at 3:41 AM, Ronald Hayden <email@hidden> wrote:
Could you file a bug with detailed steps for how to reproduce the problem?
We have been investigating it from various reports, but haven't been able
to reliably reproduce with the info we have so far.


When the problem shows up, you will likely find a docSet.dsidx- journal file
inside the Resources folder of the docsets, which can be deleted to restore
access instead of deleting the entire docset.


We believe that any doc sets updated in the last week or so should not
trigger this problem.


-- Ron

On Mar 23, 2008, at 6:04 AM, John Bishop wrote:

Xcode 3.0 corrupts the SQL indexes for its documentation sets anytime you
rebuild the codesense indexes, which includes the automatic rebuild which
occurs when you change the build SDK (to 10.4 universal, for example). It
fails 100% reliably for me in these cases. The only method I've found for
repairing the damage is to delete the docsets from any of the locations
they're saved (see Xcode preferences for the default locations) and then
have Xcode reload them. I suppose I could delete the SQL database at fault,
but I can't figure out which one(s) are the problem.


Maybe someone at Apple will destroy their own docsets so we can get this
bug fixed!


John

"Ken G. Brown" <email@hidden> said:

When I try to access anything from Xcode Help menu I get the following
error:
--
Uncaught Exception:
error during SQL execution : The database operation timed out after 30.00
seconds.


Stack Backtrace:
The stack backtrace has been logged to the console.
--

What does Xcode use to access the help items?
Where should I look for something that has gone wrong?

What can I try?

Help Viewer works fine in other applications. And I believe Sql is also
used by Yojimbo and that works fine.


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Re: Xcode 3.0 help issues (From: arri <email@hidden>)

  • Prev by Date: Is tuning possible with IB Synchronize With Xcode?
  • Next by Date: Re: Unable to debug with gdb on Mac-Intel
  • Previous by thread: Re: Xcode 3.0 help issues
  • Next by thread: not able to create NSIMage using init methods
  • Index(es):
    • Date
    • Thread