comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: Where is "Error Log"?
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Re: Where is "Error Log"? [message #57886] Tue, 08 January 2008 10:18
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
Mike Galloy writes:

> I usually make the Debug view smaller to save space, but there is one
> cool thing that you can do with it while debugging. It displays the
> call stack when your program stops -- if you click on one of the
> routines in the call stack then you can examine the variables at that
> level in the variables view.

I agree it's cool, but in 20 years of IDL programming I don't
recall ever thinking "that's something I could REALLY use!"
But, I'm keeping an open mind since I can't close the darn
thing. :-)

Cheers,

David

--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
Re: Where is "Error Log"? [message #57889 is a reply to message #57886] Tue, 08 January 2008 09:00 Go to previous message
Michael Galloy is currently offline  Michael Galloy
Messages: 1114
Registered: April 2006
Senior Member
On Jan 8, 3:50 am, David Fanning <n...@dfanning.com> wrote:
> I still haven't found the error log, but after installing
> and removing IDL 7.0 4-5 times, I've finally found the source
> of this error.
>
> Apparently, you MUST have a Debug View in either your IDL
> or Debug Perspective or IDL will throw this error. I don't
> really understand what this Debug View tells me that I don't
> know already, so I've been trying to close it in a desperate
> attempt to get more useable real estate on my display. I guess
> I'll have to live with it somewhere.

I usually make the Debug view smaller to save space, but there is one
cool thing that you can do with it while debugging. It displays the
call stack when your program stops -- if you click on one of the
routines in the call stack then you can examine the variables at that
level in the variables view.

Mike
--
www.michaelgalloy.com
Tech-X Corporation
Software Developer II
Re: Where is "Error Log"? [message #57893 is a reply to message #57889] Tue, 08 January 2008 05:43 Go to previous message
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
Vince Hradil writes:

> Look in .metadata/.log in your workspace folder
> mine is C:\Documents and Settings\hradivp\workspace\.metadata\.log

Yikes! That's a big file. Better make a note to clean that out
periodically, or I'll be looking for an even bigger hard drive. :-(

Thanks,

David

--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
Re: Where is "Error Log"? [message #57897 is a reply to message #57893] Tue, 08 January 2008 04:03 Go to previous message
Vince Hradil is currently offline  Vince Hradil
Messages: 574
Registered: December 1999
Senior Member
On Jan 8, 4:50 am, David Fanning <n...@dfanning.com> wrote:
> David Fanning writes:
>> After customizing my IDL Workbench (and getting no errors), I
>> was told I would have to restart the Workbench for changes to
>> take effect. When I do so, the Workbench starts up with several
>> errors. I get the message that "Multiple errors have occurred.
>> See error log for more details. java.lang.NullPointerException".
>
>> Where is this "error log" the Workbench speaks of?
>
> I still haven't found the error log, but after installing
> and removing IDL 7.0 4-5 times, I've finally found the source
> of this error.
>
> Apparently, you MUST have a Debug View in either your IDL
> or Debug Perspective or IDL will throw this error. I don't
> really understand what this Debug View tells me that I don't
> know already, so I've been trying to close it in a desperate
> attempt to get more useable real estate on my display. I guess
> I'll have to live with it somewhere.
>
> Cheers,
>
> David
> --
> David Fanning, Ph.D.
> Fanning Software Consulting, Inc.
> Coyote's Guide to IDL Programming:http://www.dfanning.com/
> Sepore ma de ni thui. ("Perhaps thou speakest truth.")

Look in .metadata/.log in your workspace folder
mine is C:\Documents and Settings\hradivp\workspace\.metadata\.log
Re: Where is "Error Log"? [message #57901 is a reply to message #57897] Tue, 08 January 2008 02:50 Go to previous message
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
David Fanning writes:

> After customizing my IDL Workbench (and getting no errors), I
> was told I would have to restart the Workbench for changes to
> take effect. When I do so, the Workbench starts up with several
> errors. I get the message that "Multiple errors have occurred.
> See error log for more details. java.lang.NullPointerException".
>
> Where is this "error log" the Workbench speaks of?

I still haven't found the error log, but after installing
and removing IDL 7.0 4-5 times, I've finally found the source
of this error.

Apparently, you MUST have a Debug View in either your IDL
or Debug Perspective or IDL will throw this error. I don't
really understand what this Debug View tells me that I don't
know already, so I've been trying to close it in a desperate
attempt to get more useable real estate on my display. I guess
I'll have to live with it somewhere.

Cheers,

David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Location, location, location
Next Topic: Automatic Debug Persepective

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 19:34:03 PDT 2025

Total time taken to generate the page: 0.00705 seconds