Loading Profile...
Publication : "Program bug encountered"
I've never been able to publish my libraries (be it with 2.0 and 2.0.2, and on a FTP or MobileMe).
In the little black floating window, the progress bar never appears while DL keeps telling me it is creating the files (the process is endless).
And when I Quit it, this error message shows up.
I have 180+ items, books only. And running on a french 10.5.4
I tried again, this time to a FTP server. I got this one right away.
In the little black floating window, the progress bar never appears while DL keeps telling me it is creating the files (the process is endless).
And when I Quit it, this error message shows up.
I have 180+ items, books only. And running on a french 10.5.4
I tried again, this time to a FTP server. I got this one right away.
I’m frustrated
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
The best solution from the company
-
Oh, snap. Your bug was super-simple, and super-stupid on my part. You have an unnamed shelf, that was crashing publishing because of a very simple coding error.
Thanks for finding this for me -- sorry you had to be the guinea pig.
I've fixed this in our next 2.0.3 beta, not out yet.
-Wil
I’m thankful
The company says
this solves the problem
-
Inappropriate?Sorry you're running into problems...
Let's deal with MobileMe first. The "endless creation of files" makes me think that we've dropped an exception somehow -- I added some code to catch this in 2.0.2, but apparently it's not working for you (dangit).
Can you run the "Console" program from "Applications" / "Utilities", and watch the log when you run DL2 and try to publish to MobileMe? When it hangs, you will hopefully see some kind of message in the "Console" application that says something like:
8/2/08 6:40:52 PM Delicious Library 2[6692] Uncaught exception BLAH BLAH BLAH BAD NEWS...
If you can copy/paste those lines here (or whatever lines you see from "Delicious Library 2") I can help you debug the problem.
--
I have other instructions for the FTP, but let's do one thing at a time. -
Inappropriate?BTW, the french version of 2.0.2 still show ".Mac" instead of "MobileMe" in the File menu, as well as in the preference publication windows.
So, here is this morning's log, with an attempt to MobileMe.
03/08/08 09:43:11 Delicious Library 2[695] document <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html><head><title>Index of /downloads/Delicious Library 2</title></head><body><h1>Index of /downloads/Delicious Library 2
</h1><table>
<tr><th>![[ICO]](/icons/blank.gif)
</th><th>Name</th><th>Last modified</th><th>Size</th><th>Description</th>
</tr><tr><th><hr /></th>
</tr><tr><td>![[DIR]](/icons/back.gif)
</td><td>Parent Directory</td><td> </td><td>- </td>
</tr><tr><td>![[TXT]](/icons/text.gif)
</td><td>Delicious Library 2-r10418.html</td><td>21-Jun-2008 03:59 </td><td>2.2K </td>
</tr><tr><td>![[ ]](/icons/compressed.gif)
</td><td>Delicious Library 2-r10418.zip</td><td>21-Jun-2008 04:01 </td><td>14M </td>
</tr><tr><td></td><td>Delicious Library 2-r10487.html</td><td>31-Jul-2008 21:16 </td><td>9.2K </td>
</tr><tr><td></td><td>Delicious Library 2-r10487.zip</td><td>31-Jul-2008 21:01 </td><td>14M </td>
</tr><tr><td></td><td>DeliciousLibraryVersionTwo.html</td><td>26-May-2008 21:21 </td><td>15K </td>
</tr><tr><td>![[DIR]](/icons/folder.gif)
</td><td>images/</td><td>26-May-2008 07:06 </td><td>- </td>
</tr><tr><td></td><td>releasenotes.css</td><td>26-May-2008 21:17 </td><td>879 </td>
</tr><tr><th><hr /></th>
</tr></table><address>Apache/2.2.3 (CentOS) Server at www.delicious-monster.com Port 80
</address></body></html>
03/08/08 09:43:11 Delicious Library 2[695] downloadURLs=(
http://www.delicious-monster.com/down...,
http://www.delicious-monster.com/down...
), productName=Delicious Library 2, currentVersion=10487@
03/08/08 09:43:14 Delicious Library 2[695] deallocating NSDocument 0x159d79f0
03/08/08 09:43:26 Delicious Library 2[704] document <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html><head><title>Index of /downloads/Delicious Library 2</title></head><body><h1>Index of /downloads/Delicious Library 2
</h1><table>
<tr><th></th><th>Name</th><th>Last modified</th><th>Size</th><th>Description</th>
</tr><tr><th><hr /></th>
</tr><tr><td></td><td>Parent Directory</td><td> </td><td>- </td>
</tr><tr><td></td><td>Delicious Library 2-r10418.html</td><td>21-Jun-2008 03:59 </td><td>2.2K </td>
</tr><tr><td></td><td>Delicious Library 2-r10418.zip</td><td>21-Jun-2008 04:01 </td><td>14M </td>
</tr><tr><td></td><td>Delicious Library 2-r10487.html</td><td>31-Jul-2008 21:16 </td><td>9.2K </td>
</tr><tr><td></td><td>Delicious Library 2-r10487.zip</td><td>31-Jul-2008 21:01 </td><td>14M </td>
</tr><tr><td></td><td>DeliciousLibraryVersionTwo.html</td><td>26-May-2008 21:21 </td><td>15K </td>
</tr><tr><td></td><td>images/</td><td>26-May-2008 07:06 </td><td>- </td>
</tr><tr><td></td><td>releasenotes.css</td><td>26-May-2008 21:17 </td><td>879 </td>
</tr><tr><th><hr /></th>
</tr></table><address>Apache/2.2.3 (CentOS) Server at www.delicious-monster.com Port 80
</address></body></html>
03/08/08 09:43:26 Delicious Library 2[704] downloadURLs=(
http://www.delicious-monster.com/down...,
http://www.delicious-monster.com/down...
), productName=Delicious Library 2, currentVersion=10487@
03/08/08 09:43:36 Delicious Library 2[704] *** -[NSLock lock]: deadlock (<nslock:> '(null)')
03/08/08 09:43:36 Delicious Library 2[704] *** -[NSLock unlock]: lock (<nslock:> '(null)') unlocked from thread which did not lock it
03/08/08 09:43:36 Delicious Library 2[704] *** Break on _NSLockError() to debug.
03/08/08 09:43:36 Delicious Library 2[704] *** Break on _NSLockError() to debug.
03/08/08 09:43:37 Delicious Library 2[704] *** -[NSLock unlock]: lock (<nslock:> '(null)') unlocked from thread which did not lock it
03/08/08 09:43:37 Delicious Library 2[704] *** -[NSLock lock]: deadlock (<nslock:> '(null)')
03/08/08 09:43:37 Delicious Library 2[704] *** Break on _NSLockError() to debug.
03/08/08 09:43:37 Delicious Library 2[704] *** Break on _NSLockError() to debug.
03/08/08 09:43:37 Delicious Library 2[704] *** +[NSCFDictionary cancelUserAttentionRequest:]: unrecognized selector sent to class 0xa067f720
03/08/08 09:43:37 Delicious Library 2[704] *** +[NSCFDictionary cancelUserAttentionRequest:]: unrecognized selector sent to class 0xa067f720
03/08/08 09:44:19 Delicious Library 2[704] NSExceptionHandler has recorded the following exception:
NSUncaughtSystemExceptionException -- Uncaught system exception: signal 11
Stack trace: 0x26021e 0x900ab09b 0xffffffff 0x125b60 0x7ef9a 0x968d4955 0x471f 0x15539 0x95094c23 0x153d2 0x95143660 0x95143365 0x95142feb 0x95141890 0x9505e853 0x94fbbe27 0x94f89030 0x355a 0x2
03/08/08 09:44:31 com.apple.launchd[66] ([0x0-0xa00a0].com.delicious-monster.library2[704]) Exited: Terminated </nslock:></nslock:></nslock:></nslock:> -
Inappropriate?Hrm. Ok, not much to go on there. I was hoping for an earlier error.
Looks like some kind of memory-allocation bug, but I can't replicate it on my machine. I've set my machine to speak French and published using both templates to MobileMe, and it doesn't crash for me.
Ok, this is a little more advanced, but if you can launch Terminal, and at the prompt, type:
gdb /Applications/Delicious\ Library\ 2.app/Contents/MacOS/Delicious\ Library\ 2[return]
You should see:
GNU gdb 6.3.50-20050815 (Apple version gdb-960) (Sun May 18 18:38:33 UTC 2008)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-apple-darwin"...Reading symbols for shared libraries .................................... done
[...]
(gdb)
Type:
break objc_exception_throw[return]
You should see:
Breakpoint 1 at 0x1324f0d7
(gdb)
Type:
run[return]
You should see:
Starting program: /Applications/Delicious Library 2.app/Contents/MacOS/Delicious Library 2
[...]
Try publishing again, and when the program hangs, go back to Terminal and type:
where[return]
And let me know what it says.
Phew! -
Inappropriate?Couldn't do much.
I've got a "-bash: gdb: command not found" at step 1...
If you think having my library can help you, I can drop an archive on a FTP for you to use it.
-
Inappropriate?Yah, whoops, sorry -- forgot most people don't have those tools installed.
I'm elbow-deep in the FTP code right now, but as soon as MobileMe seems to work for me (I can't sync or talk to it) I'll try to get you a build of it that uses a different access framework, to test my theory it's a bug in the (old) dotMacKit framework I'm using from Apple.
-W -
Inappropriate?I've released a beta of V2.0.3, which changes how we access MobileMe and fixes many problems with publishing. If you had troubles publishing to MobileMe, then please try again with this version.
http://delicious-monster.com/download...
Here are the complete release notes:
http://delicious-monster.com/download...
I’m happy
-
Inappropriate?Thins go a little bit better (the progress bar showing the state of the publication now appears) but its stops at the third page and then nothing happens, the window stay idle. Hitting Cancel does nothing. That's for MobileMe
The same goes for the FTP publication except that I get an error message when I want to quit ("operation couldn't end... bla bla bla")
I’m undecided
-
Inappropriate?Innocente: Apparently I'm not going to be able to figure this one out unless I have your library... I've tried running in French, and with the templates you are using, and it works for me.
Are you ok with sharing it? Can you mail it to wjs at me.com? -
Inappropriate?Oh, snap. Your bug was super-simple, and super-stupid on my part. You have an unnamed shelf, that was crashing publishing because of a very simple coding error.
Thanks for finding this for me -- sorry you had to be the guinea pig.
I've fixed this in our next 2.0.3 beta, not out yet.
-Wil
I’m thankful
The company says
this solves the problem
-
EMPLOYEE
