| Re: EOS_SW_CREATE HDF function file path issue [message #80189] |
Thu, 10 May 2012 13:02 |
Jim Pendleton
Messages: 165
Registered: November 2011
|
Senior Member |
|
|
On Thursday, May 10, 2012 12:00:25 PM UTC-6, Edward Hyer wrote:
> On Thursday, May 10, 2012 10:24:35 AM UTC-7, jimmylee...@gmail.com wrote:
>> Can you show an example of the string you're using for FULL_PATH? Perhaps it's a function of escapes needed by one internal routine or another.
>
> /shared/aerosol_dev2/users/hyer/calsrc/mod04_landocean_idl_s andbox/aux/hdfeos/201205/2012051000_obsnew.hdf
>
> Too long? Doesn't like directories that are only numbers?
I would recommend sending this example to support@exelisvis.com. The file name length limit should be 255 characters, and you're clearly short of that. Perhaps there's an internal routine that didn't get the memo. Also your subject line references the *CREATE routine, but your example shows *OPEN.
|
|
|
|
| Re: EOS_SW_CREATE HDF function file path issue [message #80190 is a reply to message #80189] |
Thu, 10 May 2012 11:00  |
MarioIncandenza
Messages: 231
Registered: February 2005
|
Senior Member |
|
|
On Thursday, May 10, 2012 10:24:35 AM UTC-7, jimmylee...@gmail.com wrote:
> Can you show an example of the string you're using for FULL_PATH? Perhaps it's a function of escapes needed by one internal routine or another.
/shared/aerosol_dev2/users/hyer/calsrc/mod04_landocean_idl_s andbox/aux/hdfeos/201205/2012051000_obsnew.hdf
Too long? Doesn't like directories that are only numbers?
|
|
|
|
| Re: EOS_SW_CREATE HDF function file path issue [message #80191 is a reply to message #80190] |
Thu, 10 May 2012 10:24 |
Jim Pendleton
Messages: 165
Registered: November 2011
|
Senior Member |
|
|
On Thursday, May 10, 2012 10:37:13 AM UTC-6, Edward Hyer wrote:
> So, I think I got this working, but having found nothing on the Googs
> about this problem, I am posting to the newsgroup so there will be a
> reference, and maybe someone can shed some light on the root cause.
>
> Symptom: Adding data to HDF-EOS file created with EOS_SW_OPEN() causes
> a segfault-- IDL crashes. The specific circumstance of the crash seems
> to be opening an existing HDF-EOS file using EOS_SW_OPEN().
> Resolution: The crash occurs at:
> HDFEOS_FID = EOS_SW_OPEN(FULL_PATH,/RDWR)
> The crash does not occur if this is substituted with
> CD,FILE_DIRNAME(FULL_PATH)
> HDFEOS_FID = EOS_SW_OPEN(FILE_BASENAME(FULL_PATH),/RDWR)
>
> Anyway, that's a weird one and took a while to debug, so I'm posting
> it here if anyone in the future is foolish enough to try to use IDL
> for this.
Can you show an example of the string you're using for FULL_PATH? Perhaps it's a function of escapes needed by one internal routine or another.
Jim P.
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
