| Re: idlwave segfault [message #69278] |
Tue, 12 January 2010 07:23  |
Bruce Bowler
Messages: 128
Registered: September 1998
|
Senior Member |
|
|
On Mon, 11 Jan 2010 10:12:24 -0800, pp wrote:
> On Jan 11, 4:02 pm, Bruce Bowler <bbow...@bigelow.org> wrote:
>>
>> No ideas?
>
> Only the trivial: You did not explicitly say whether the segfault only
> occurs when using IDL from Emacs. Did you check that IDL works when you
> call IDL alone, directly from the command line? To make sure it is just
> an idlwave problem, and not an idl problem.
You are correct, I didn't explicitly state that I tried that.
I did try (and succeed) in launching and using IDL from a shell prompt so
it appears to me that it's strictly an idlwave problem, not a more
generic IDL issue.
Bruce
--
+-------------------+--------------------------------------- ------------+
Bruce Bowler | Good things come to those who procrastinate. -
1.207.633.9600 | Julie Mougey
bbowler@bigelow.org |
+-------------------+--------------------------------------- ------------+
|
|
|
|
|
|
| Re: idlwave segfault [message #69288 is a reply to message #69287] |
Mon, 11 January 2010 10:02  |
Bruce Bowler
Messages: 128
Registered: September 1998
|
Senior Member |
|
|
On Thu, 07 Jan 2010 13:52:10 +0000, Bruce Bowler wrote:
> On Tue, 05 Jan 2010 19:06:43 +0000, Bruce Bowler wrote:
>
>> I'm pretty sure I've seen this mentioned before but google isn't
>> helping me find it if I'm correct...
>>
>> I'm running Fedora 10, Emacs 22.3.1 and idlwave 6.1_em22 (all
>> "defaults" for F10, as far as I know).
>>
>> When I try to start an IDL shell from within emacs (via C-c C-s), I get
>> a few messages that scroll by too fast for me to see them and then that
>> "old favorite"
>>
>> Fatal error (11)Segmentation fault
>>
>> What am I doing wrong???
>>
>> Bruce
>
> More info in the event that it helps.
>
> If I start the shell with C-c C-l the shell successfully starts, but as
> soon as I enter the *idl* buffer, I get the segfault.
>
> I can't say for sure when this started since it's been a while since
> I've done much/any IDL editing...
>
> Thanks for any help and/or suggestions you might have to offer.
No ideas?
--
+-------------------+--------------------------------------- ------------+
Bruce Bowler | In theory, there is no difference between theory
1.207.633.9600 | and practice. In practice, there is. - Anon
bbowler@bigelow.org |
+-------------------+--------------------------------------- ------------+
|
|
|
|
| Re: idlwave segfault [message #69416 is a reply to message #69278] |
Tue, 12 January 2010 11:34 |
JDS
Messages: 94
Registered: March 2009
|
Member |
|
|
On Jan 12, 10:23 am, Bruce Bowler <bbow...@bigelow.org> wrote:
> On Mon, 11 Jan 2010 10:12:24 -0800, pp wrote:
>> On Jan 11, 4:02 pm, Bruce Bowler <bbow...@bigelow.org> wrote:
>
>>> No ideas?
>
>> Only the trivial: You did not explicitly say whether the segfault only
>> occurs when using IDL from Emacs. Did you check that IDL works when you
>> call IDL alone, directly from the command line? To make sure it is just
>> an idlwave problem, and not an idl problem.
>
> You are correct, I didn't explicitly state that I tried that.
>
> I did try (and succeed) in launching and using IDL from a shell prompt so
> it appears to me that it's strictly an idlwave problem, not a more
> generic IDL issue.
There are various reasons why this test isn't conclusive. One of the
main problems has to do with the environment present in the Emacs
session vs. your shell. I've seen segfaults in IDL based on
incorrectly set DISPLAY parameters, and other things. Launch emacs
from the shell with emacs -q to skip your .emacs init file, and see if
that changes anything.
JD
|
|
|
|
| Re: idlwave segfault [message #69417 is a reply to message #69278] |
Tue, 12 January 2010 10:22 |
Matt[2]
Messages: 69
Registered: March 2007
|
Member |
|
|
Bruce Bowler <bbowler@bigelow.org> writes:
> You are correct, I didn't explicitly state that I tried that.
>
> I did try (and succeed) in launching and using IDL from a shell prompt so
> it appears to me that it's strictly an idlwave problem, not a more
> generic IDL issue.
Bruce,
Can you see if you have an old version of idlwave installed?
M-x list-load-path-shadows
When it crashes, what's left in the *messages* buffer, any clues there?
Matt
--
Matthew Savoie - Scientific Programmer
National Snow and Ice Data Center
(303) 735-0785 http://nsidc.org
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
