Welcome to iraf.net Sunday, November 23 2014 @ 11:21 PM MST


 Forum Index > Help Desk > General IRAF New Topic Post Reply
 iraf 2.16 fxheader problem
   
rjvo
 06/10/2012 09:19AM (Read 2969 times)  
+++++
Active Member

Status: offline


Registered: 04/21/2007
Posts: 127
I run the command:
[code:1:9f5df84caf]fxheader *.fz lo+ > z[/code:1:9f5df84caf]
and everything is going well except one file (which is a correct one in DS9):
[code:1:9f5df84caf]Warning: Cannot open file (q1186.fits.f)[/code:1:9f5df84caf]
The file "[b:9f5df84caf]q1186.fits.fz[/b:9f5df84caf]" exists and I can make:
[code:1:9f5df84caf]fitsutil> fxheader q1186.fits.fz lo+[/code:1:9f5df84caf]
with no problem.

 
Profile Email
 Quote
fitz
 06/10/2012 09:19AM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 3624
How many images does the template "*.fz" turn out to be? I noticed the warning message prints the image name as "...fits.f" and not "...fits.fz" so I'm wondering whether the template expansion may be truncating the name in list somehow. One way to test this is to set[code:1:ad1b455cbd]
cl> reset use_new_imt = no
cl> flpr 0 # zero, not oh
[/code:1:ad1b455cbd]This will use the older template code and if it then works would help confirm the truncation. OTOH, it could be something like unitialized code in the task, but I'm not able to reproduce the problem myself. If you still have problems, could you tell me what IRAF version and platform you're using? If its v2.16, are you sure you're running the latest update?

 
Profile Email
 Quote
rjvo
 06/10/2012 09:19AM  
+++++
Active Member

Status: offline


Registered: 04/21/2007
Posts: 127
As we can see from the pattern [b:9ca9b71935]fxheader *.fz lo+ > z[/b:9ca9b71935] there must be a bug in the task. There is a file number (1186) in the file name, so the template list is rather big.

 
Profile Email
 Quote
rjvo
 06/10/2012 09:19AM  
+++++
Active Member

Status: offline


Registered: 04/21/2007
Posts: 127
I updated today the iraf 2.16 to:
[code:1:f54051f4fb]NOAO/IRAF PC-IRAF Revision 2.16 EXPORT Thu May 24 15:41:17 MST 2012[/code:1:f54051f4fb]
and the the situation is the same:
[code:1:f54051f4fb]fitsutil> fxheader *.fz lo+ > zz
Warning: Cannot open file (q1186.fits.f)
fitsutil> reset use_new_imt = no
fitsutil> flpr 0
fitsutil> del zz
fitsutil> fxheader *.fz lo+ > zz
fitsutil> [/code:1:f54051f4fb]
As we can see, there is no problem when I reset [b:f54051f4fb]use_new_imt[/b:f54051f4fb].

 
Profile Email
 Quote
fitz
 06/10/2012 09:19AM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 3624
I do remember fixing a bug with long-template expansion recently and it appears this was done in the dev system after the last binary release of the external packages. The extpkg distros have just been updated so I'd suggest doing[code:1:4c03d24492]
% cd $iraf/extern
% make fitsutil
[/code:1:4c03d24492]to reinstall the FITSUTIL package binaries. A "cd $iraf ; make latest" will also make sure the core IRAF system and remaining packages are updated as well.

 
Profile Email
 Quote
rjvo
 06/10/2012 09:19AM  
+++++
Active Member

Status: offline


Registered: 04/21/2007
Posts: 127
I did today:
[code:1:618e4f87a0]cd $iraf
make latest[/code:1:618e4f87a0]
and after starting it I got:
[code:1:618e4f87a0]fitsutil> fxheader *.fz lo+ > zz
*** glibc detected *** /iraf/iraf/extern/fitsutil/bin.linux/x_fitsutil.e: realloc(): invalid next size: 0x0b855008 ***
======= Backtrace: =========
/lib/i686/cmov/libc.so.6(+0x6b381)[0x400dd381]
/lib/i686/cmov/libc.so.6(+0x70aad)[0x400e2aad]
/lib/i686/cmov/libc.so.6(realloc+0xdd)[0x400e2d8d]
/iraf/iraf/extern/fitsutil/bin.linux/x_fitsutil.e[0x810efe9]
/iraf/iraf/extern/fitsutil/bin.linux/x_fitsutil.e[0x80f0154]
/iraf/iraf/extern/fitsutil/bin.linux/x_fitsutil.e[0x80f13de]
/iraf/iraf/extern/fitsutil/bin.linux/x_fitsutil.e[0x80d62ed]
/iraf/iraf/extern/fitsutil/bin.linux/x_fitsutil.e[0x80595a5]
/iraf/iraf/extern/fitsutil/bin.linux/x_fitsutil.e[0x80587f4]
/iraf/iraf/extern/fitsutil/bin.linux/x_fitsutil.e[0x804f4f2]
/iraf/iraf/extern/fitsutil/bin.linux/x_fitsutil.e[0x804d6b9]
/iraf/iraf/extern/fitsutil/bin.linux/x_fitsutil.e[0x80ed052]
/iraf/iraf/extern/fitsutil/bin.linux/x_fitsutil.e[0x8056eed]
/lib/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0x40088ca6]
/iraf/iraf/extern/fitsutil/bin.linux/x_fitsutil.e[0x804d3a1]
======= Memory map: ========
08048000-082c1000 r-xp 00000000 08:07 408861 /iraf/iraf/extern/fitsutil/bin.linux/x_fitsutil.e
082c1000-082d5000 rwxp 00279000 08:07 408861 /iraf/iraf/extern/fitsutil/bin.linux/x_fitsutil.e
082d5000-0a895000 rwxp 00000000 00:00 0
0b827000-0b86d000 rwxp 00000000 00:00 0 [heap]
40000000-4001b000 r-xp 00000000 08:07 484544 /lib/ld-2.11.3.so
4001b000-4001c000 r-xp 0001b000 08:07 484544 /lib/ld-2.11.3.so
4001c000-4001d000 rwxp 0001c000 08:07 484544 /lib/ld-2.11.3.so
4001d000-4001e000 r-xp 00000000 00:00 0 [vdso]
4001e000-40020000 rwxp 00000000 00:00 0
40032000-40056000 r-xp 00000000 08:07 499135 /lib/i686/cmov/libm-2.11.3.so
40056000-40057000 r-xp 00023000 08:07 499135 /lib/i686/cmov/libm-2.11.3.so
40057000-40058000 rwxp 00024000 08:07 499135 /lib/i686/cmov/libm-2.11.3.so
40058000-4006d000 r-xp 00000000 08:07 499143 /lib/i686/cmov/libpthread-2.11.3.so
4006d000-4006e000 r-xp 00014000 08:07 499143 /lib/i686/cmov/libpthread-2.11.3.so
4006e000-4006f000 rwxp 00015000 08:07 499143 /lib/i686/cmov/libpthread-2.11.3.so
4006f000-40072000 rwxp 00000000 00:00 0
40072000-401b2000 r-xp 00000000 08:07 499153 /lib/i686/cmov/libc-2.11.3.so
401b2000-401b3000 ---p 00140000 08:07 499153 /lib/i686/cmov/libc-2.11.3.so
401b3000-401b5000 r-xp 00140000 08:07 499153 /lib/i686/cmov/libc-2.11.3.so
401b5000-401b6000 rwxp 00142000 08:07 499153 /lib/i686/cmov/libc-2.11.3.so
401b6000-401ba000 rwxp 00000000 00:00 0
401ba000-401d7000 r-xp 00000000 08:07 482387 /lib/libgcc_s.so.1
401d7000-401d8000 rwxp 0001c000 08:07 482387 /lib/libgcc_s.so.1
40200000-40221000 rwxp 00000000 00:00 0
40221000-40300000 ---p 00000000 00:00 0
bfa82000-bfa97000 rwxp 00000000 00:00 0 [stack][/code:1:618e4f87a0]
The Ctrl-C brakes it with: [b:618e4f87a0]PANIC in `/iraf/iraf/extern/fitsutil/bin.linux/x_fitsutil.e': software terminate (interrupt)[/b:618e4f87a0] and then [b:618e4f87a0]lo[/b:618e4f87a0] gives: [b:618e4f87a0]Abnormal termination of child process 'fitsutilbin$x_fitsutil.e'
Fatal logout error. CL dies.[/b:618e4f87a0].
Anyway when I start IRAF again:
[code:1:618e4f87a0]cl
vocl> fitsutil
fitsutil> fxheader b0001.fits.fz lo+[/code:1:618e4f87a0]
I get a correct answer and NO IRAF PANIC.

 
Profile Email
 Quote
fitz
 06/10/2012 09:19AM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 3624
I can confirm there's still a problem in the template code for very long strings and will fix it for the next update. Until then, use the workaround. I'll let you know when the update is available.

 
Profile Email
 Quote
   
Content generated in: 0.51 seconds
New Topic Post Reply

Normal Topic Normal Topic
Sticky Topic Sticky Topic
Locked Topic Locked Topic
New Post New Post
Sticky Topic W/ New Post Sticky Topic W/ New Post
Locked Topic W/ New Post Locked Topic W/ New Post
View Anonymous Posts 
Anonymous users can post 
Filtered HTML Allowed 
Censored Content 


Privacy Policy
Terms of Use

User Functions

Login