how to debug?

ssa · Posted: Mon Jan 12, 2004 3:56 pm Post subject: how to debug?

What's the best way to debug NeoOffice ? I can't even manage to start it from the console.

Can I somehow launch it under the debugger's control ?

Problem is (when I launch it via its icon) that it crashes upon displaying the splashscreen.

Stephan

---

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x0000001d

Thread 0 Crashed:
0 com.apple.QD 0x94954efc DisposeGWorld + 0xc4
1 libvcl641mxp.dylib 0x0175e680 _._11SalGraphics + 0x88
2 libvcl641mxp.dylib 0x01761ce0 _._16SalVirtualDevice + 0x2c
3 libvcl641mxp.dylib 0x01764588 DestroyVirtualDevice__11SalInstanceP16SalVirtualDevice + 0x1c
4 libvcl641mxp.dylib 0x01763328 Destroy__9SalBitmap + 0x44
5 libvcl641mxp.dylib 0x01763024 _._9SalBitmap + 0x1c
6 libvcl641mxp.dylib 0x01637db0 _._9ImpBitmap + 0x2c
7 libvcl641mxp.dylib 0x01609bfc ImplReleaseRef__6Bitmap + 0x4c
8 libvcl641mxp.dylib 0x01608d98 _._6Bitmap + 0x1c
9 libvcl641mxp.dylib 0x0161e660 _._8BitmapEx + 0x30
10 libvcl641mxp.dylib 0x01695b20 _._13ImplWallpaper + 0x2c
11 libvcl641mxp.dylib 0x0169690c __as__9WallpaperRCB0 + 0x58
12 libvcl641mxp.dylib 0x01660efc SetBackground__12OutputDevice + 0x34
13 libvcl641mxp.dylib 0x016a4800 ImplInit__16ImplBorderWindowP6WindowUlUsP16SystemParentData + 0xc0
14 libvcl641mxp.dylib 0x016a48d4 __16ImplBorderWindowP6WindowP16SystemParentDataUlUs + 0x58
15 libvcl641mxp.dylib 0x016ee140 ImplInit__10WorkWindowP6WindowUlP16SystemParentData + 0x54
16 libvcl641mxp.dylib 0x016ee41c __10WorkWindowP6WindowUl + 0x54
17 soffice.bin 0x000154b8 __16IntroWindow_ImplRC6Bitmap + 0x34
1

fa · The Architect Joined: May 27, 2003 Posts: 88

Stephan,

You have a _really_ older version of NeoOffice then. VirtualDevices haven't been Carbon/QuickDraw based since last year early. Pull from HEAD.

Second, what you do is drop all the applications into a bundle.

1) Download http://www.iceni.org/~dan/NeoOffice.app.tar.gz
2) Install NeoOffice to a temp dir using instsetoo/unxmacxp.pro/01/normal/setup -v -nogui -r:script where 'script' is a regular install script file
3) Drag each folder from your aqua install temp folder _into_ the folder here:

help -> into Contents/
cp -r program/* -> Contents/MacOS/
share -> into Contents/
user -> into Contents/

4) Copy the macosx_extras/graphics/NeoOffice.icns -> Contents/Resources

And you should now have a double-clickable application...

For debugging, you'll either have to use gdb or start using debugging fprintfs Smile

If you need any help, just give me a yell on IRC tomorrow or whenever.

Dan

ssa · Posted: Tue Jan 13, 2004 1:14 am Post subject:

schlesi · Posted: Tue Jan 13, 2004 2:21 pm Post subject:

Stephan,

you can find up-to-date build-instructions in our NeoWiki: http://sixthcrusade.com/neowiki/index.php?page=BuildInstructions.

I hope, that helps.

Thomas

ssa · Posted: Tue Jan 13, 2004 3:40 pm Post subject:

On the NeoWiki there are some typos, regarding the install and setup directories. I guess it is
cd /neooffice-setup
before running ./install.

But the bigger problem is, that both links regarding the torso download do not work. I get permission denied on the ftp link and the http link is empty.....

Perhaps, you can have a look ?

Stephan

jakeOSX · Ninja Joined: Aug 12, 2003 Posts: 1373

I checked the server and the link for sixthcrusade and the torso is still there. if the link isn't working for you (did you try to 'download target'?) then you can try just going to

http://neo-downloads.sixthcrusade.com

and finding it there.

-j

schlesi · Posted: Wed Jan 14, 2004 1:08 pm Post subject:

Stephan,

thanks for your hint. I have corrected my typo error in the NeoWiki.

An I will have a look at my ftp-server. I've had to re-install my Linux-box after trying to update my kernel from 2.4 to 2.6 and misconfigured it very hard ;-(

Thomas

ssa · Posted: Wed Jan 14, 2004 3:26 pm Post subject:

Thomas,

what is the neooffice-install directory good for when you later start the setup with -prefix=/xxx which leaves that directory empty ?
And if that directory is not used, setting the DYLD_LIBRARY_PATH is perhaps also not required ? And wouldn't we need a setenv here, assuming tcsh is used.

Sorry for all those questions, but perhaps others are confused, too...

Stephan Wink

schlesi · Posted: Thu Jan 15, 2004 12:15 pm Post subject:

Stephan,

the build-instructions have historically grown from the old "flaming yeti" instructions. You are right, the instructions could be a little bit confusing Wink

I have "modernized" the instructions in the Wiki. Thank you for your suggestion.

Thomas