Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Programming / Mac Programming / April 2006



Tip: Looking for answers? Try searching our database.

How troubleshoot an application bundle

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
surferwill@gmail.com - 17 Apr 2006 17:29 GMT
Hi,

I have an application bundle I created with an older version of
InstallAnywhere.  It almost works!  It looks like its loading, briefly
shows the application name on the menu bar, then quits.

Is there someway to trouble shoot this?  Can I start the app from the
command line somehow or look at a log file somewhere to see what went
wrong?  I assume I have a file misplaced or a classpath not set right,
but if you can't see any error messages what can I do?

Thanks in advance,
-Will
SM Ryan - 17 Apr 2006 20:07 GMT
# Hi,
#
# I have an application bundle I created with an older version of
# InstallAnywhere.  It almost works!  It looks like its loading, briefly
# shows the application name on the menu bar, then quits.
#
# Is there someway to trouble shoot this?  Can I start the app from the
# command line somehow or look at a log file somewhere to see what went
# wrong?  I assume I have a file misplaced or a classpath not set right,
# but if you can't see any error messages what can I do?

Open a Terminal window. Drag and drop the application icon from
Finder onto the Terminal window. That will insert the path up to
.app. Backspace over the trailing space, and type in
Contents/MacOS/executablename (tabbing if your shell supports it).

That gives you the command line to the executable. You can add
program parameters, if any, and hit return. That will launch the
application with stdin, stdout, and stderr attached to the Terminal
window. You can also run command line gdb here.

You can also run multiple invocations of the application from different
Terminal windows.

--
SM Ryan http://www.rawbw.com/~wyrmwif/
Death is the worry of the living. The dead, like myself,
only worry about decay and necrophiliacs.
Simon Slavin - 24 Apr 2006 18:08 GMT
On 17/04/2006, surferwill@gmail.com wrote in message
<1145291348.813312.194110@e56g2000cwe.googlegroups.com>:

> I have an application bundle I created with an older version of
> InstallAnywhere.  It almost works!

Do you absolutely definitely /need/ it to have an installer ?  Can you not
just prepare an application icon or folder for the user to drag wherever
they want it ?

Simon.
Signature

http://www.hearsay.demon.co.uk

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.