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

Home » Public Forums » archive » Go figure
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
Go figure [message #65439] Wed, 04 March 2009 07:35 Go to next message
lbnc is currently offline  lbnc
Messages: 15
Registered: January 2005
Junior Member
Hi there,

now have a look at this:

IDL> print, !version
{ x86_64 linux unix linux 6.2 Jun 20 2005 64 64}
IDL> .comp ../idl_lib/graphics/colorbar.pro
% Compiled module: COLORBAR.
IDL> .r ntest
% Compiled module: $MAIN$.
% Compiled module: CONGRID.
IDL> .r ntest
*** glibc detected *** corrupted double-linked list:
0x000000351f330698 ***
Aborted
[lbnc1@ion2 idl]$

Interesting, Mr. Bond. Here is the code for ntest.pro:

mind = 0.3
maxd = 0.8
ynames = string(fltarr((maxd-mind)*10.+1)/10., format='(F3.1)')

colorbar, /vert, $
ytickname=ynames

end

Alternatively, I sometimes get the following error
*** glibc detected *** double free or corruption (fasttop):
0x00000000007d0b90 ***
Aborted

Can anybody recreate that? It crashed when ntest is called the second
time, or, alternatively, when you recompile colorbar. colorbar is the
routine provided by David. Does anybody have an idea what is wrong? As
far as my tests go, both arguments (vert and ytickname) have to be set
to create this error.

Ah, and

ynames = replicate('0.0', 6)

works like a charm.

Cheers
Lasse Clausen
Re: Go figure [message #65511 is a reply to message #65439] Thu, 05 March 2009 05:44 Go to previous message
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
lbnc@lbnc.de writes:

> Downloaded the latest version and used ticknames, works swimmingly. It
> still crashes with the ytickname keyword, though. I don't know why but
> frankly, my dear, I don't give a damn. I just thought I'd share this
> information with you guys. One fine day I might start commenting out
> stuff from colorbar.pro and see which code is the culprit. Seeing that
> the actual error is thrown by glibc doesn't exactly make debugging
> easier.

Off-hand, if I were going looking for the problem (and I'm
not going to either!), I would look at what happens when
keywords in _EXTRA are the same as keywords that are
expressed on the command line. I can see room for confusion
there. :-)

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: break point test e.g. Petitt test
Next Topic: Re: Treating an object as a structure

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

Current Time: Sat Oct 11 08:39:01 PDT 2025

Total time taken to generate the page: 2.87972 seconds