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

Home » Public Forums » archive » Segmentation Fault
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: segmentation fault [message #18273 is a reply to message #10754] Sat, 04 December 1999 00:00 Go to previous message
davidf is currently offline  davidf
Messages: 2866
Registered: September 1996
Senior Member
Bill Gross (gross@chuma.cas.usf.edu) writes:

> I'm looking for some expert help....well...any kind of help !

Oh, well, if any kind of help will do, I can help. :-)

> I am running a procedure that I have written in IDL using the solaris
> x86 operating system...I continually make modifications to my method
> of analysis, so I frequently break out of the program to "RETALL" and
> begin again....
>
> Unfortunately, after typing "RETALL", I now get the following message
> from IDL..
> temporary variables are still checked out-cleaning up...
>
> and then the OS gives a segmentation fault.
>
> I know I'm not running out of swap space, and a call to "TOP" shows
> that I'm taking about 20 mb with my IDL application ( have 128 mb in
> system) and I've checked (and increased) the stack size and file
> descriptor limits for the OS....
>
> Can anyone give me any hints on what I should look for next ??

Uh, well, I would look for a good book on program
interface design. :-)

When your program calls a procedure or function, and that
procedure or function needs some variables, it gets them.
If you kill the program while you are two or three levels
deep, you will leave those temporary variables dangling when
you RETurn ALL the way back to the main level. So IDL tries
to clean up after you. Hence, the message you get.

I often (too often!) see the message when I've crashed
a program in an event handler, for example, since the
event handler is called from within XMANAGER.

I'm not sure why you are getting a segmentation fault,
however. You are probably going to have to ask the
good folks at RSI about that. Normally, IDL just
carries on after returning as if nothing had happened.

I would reconsider your program design, however, to allow
better interactivity than just killing the darn thing
and starting over. That seems just a tad retro to me.
Kind of like the way I wrote FORTRAN programs in the
late 1970's. How about a pop-up dialog that asked if
you want to continue program execution at various stages
of the analysis. Something you could turn off, for example,
once you got the process figured out. Or maybe a slider
attached to one of the parameters so you could interactively
change the parameter value instead of having to start
over.

> ( Dave Fanning...I know you're lurking out there somewhere !)

I've never lurked on this newsgroup a day in my life. :-)

Cheers,

David
--
David Fanning, Ph.D.
Fanning Software Consulting
Phone: 970-221-0438 E-Mail: davidf@dfanning.com
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: LMFIT
Next Topic: Re: How to select best from a long list?

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

Current Time: Mon Apr 27 10:21:41 PDT 2026

Total time taken to generate the page: 1.99688 seconds