Welcome to iraf.net Friday, May 17 2024 @ 04:57 AM GMT


 Forum Index > Help Desk > Systems New Topic Post Reply
 update of glibc results in iraf crashing:
   
wkerzendorf
 03/21/2006 01:17AM (Read 5472 times)  
+----
Newbie

Status: offline


Registered: 03/20/2006
Posts: 7
Here is the error
[code:1:55ea8a67f7]*** glibc detected *** /iraf/iraf/noao/bin.redhat/x_onedspec.e: corrupted double-linked list: 0x00b3b8b8 ***
======= Backtrace: =========
/lib/libc.so.6[0xa77b71]
/lib/libc.so.6[0xa780a9]
/lib/libc.so.6(__libc_free+0x77)[0xa7865f]
/iraf/iraf/noao/bin.redhat/x_onedspec.e[0x81e00b8]
/iraf/iraf/noao/bin.redhat/x_onedspec.e[0x81b8031]
/iraf/iraf/noao/bin.redhat/x_onedspec.e[0x80dd7e2]
/iraf/iraf/noao/bin.redhat/x_onedspec.e[0x8098c9e]
/iraf/iraf/noao/bin.redhat/x_onedspec.e[0x80519b6]
/iraf/iraf/noao/bin.redhat/x_onedspec.e[0x804a6c8]
/iraf/iraf/noao/bin.redhat/x_onedspec.e[0x81b2da0]
/iraf/iraf/noao/bin.redhat/x_onedspec.e[0x811f24c]
/lib/libc.so.6(__libc_start_main+0xdf)[0xa29d5f]
/iraf/iraf/noao/bin.redhat/x_onedspec.e(log+0x8d)[0x804a1d1]
======= Memory map: ========
009f7000-00a11000 r-xp 00000000 fd:00 8872535 /lib/ld-2.3.5.so
00a11000-00a12000 r-xp 00019000 fd:00 8872535 /lib/ld-2.3.5.so
00a12000-00a13000 rwxp 0001a000 fd:00 8872535 /lib/ld-2.3.5.so
00a15000-00b38000 r-xp 00000000 fd:00 8872536 /lib/libc-2.3.5.so
00b38000-00b3a000 r-xp 00123000 fd:00 8872536 /lib/libc-2.3.5.so
00b3a000-00b3c000 rwxp 00125000 fd:00 8872536 /lib/libc-2.3.5.so
00b3c000-00b3e000 rwxp 00b3c000 00:00 0
00b40000-00b63000 r-xp 00000000 fd:00 8872538 /lib/libm-2.3.5.so
00b63000-00b64000 r-xp 00022000 fd:00 8872538 /lib/libm-2.3.5.so
00b64000-00b65000 rwxp 00023000 fd:00 8872538 /lib/libm-2.3.5.so
00d7c000-00d85000 r-xp 00000000 fd:00 8872544 /lib/libgcc_s-4.0.2-20051126.so.1
00d85000-00d86000 rwxp 00009000 fd:00 8872544 /lib/libgcc_s-4.0.2-20051126.so.1
08048000-081f3000 r-xp 00000000 fd:00 1872370 /iraf/irafbin/noao.bin.redhat/x_onedspec.e
081f3000-0822a000 rwxp 001aa000 fd:00 1872370 /iraf/ir0822a000-08339000 rwxp 0822a000 00:00 0
0974f000-09d8a000 rwxp 0974f000 00:00 0 [heap]
40000000-40001000 r-xp 40000000 00:00 0 [vdso]
40001000-40002000 rwxp 40001000 00:00 0
40020000-40054000 rwxp 40020000 00:00 0
40087000-40090000 r-xp 00000000 fd:00 8871508 /lib/libnss_files-2.3.5.so
40090000-40091000 r-xp 00008000 fd:00 8871508 /lib/libnss_files-2.3.5.so
40091000-40092000 rwxp 00009000 fd:00 8871508 /lib/libnss_files-2.3.5.so
40092000-40515000 rwxp 40092000 00:00 0
40600000-40621000 rwxp 40600000 00:00 0
40621000-40700000 --xp 40621000 00:00 0
bfbd5000-bfbeb000 rwxp bfbd5000 00:00 0 [stack]
afbin/noao.bin.redhat/x_onedspec.e[/code:1:55ea8a67f7]
I updated my system to glibc-3.5-10 on fedora core 4.
I also recompiled the iraf packages but without any success. The xgterm is displaying the following message (when running the task ecidentify):
warning: smw_mw: spectrum not found.Hopefully someone know how to elivaite this.
Thanks in advance
Wolfgang Kerzendorf

 
Profile Email
 Quote
fitz
 03/21/2006 01:17AM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040
Hi Wolfgang, I'm a bit confusde by your message, did you mean GCC 3.5 (the latest glibc is I think 2.4)? It may not make a difference, but I assume you mean this was running on the same data before the upgrade but not after? The specific "spectrum not found" error message occurs when the spectral WCS doesn't match the data, e.g. it defines more spectra than are in the image. Double check that the DISPAXIS keyword in the image header is correct for the file or if it doesn't exist that the 'dispaxis' ECHELLE package parameter is set appropriately (e.g. "cl> epar echelle" to reset it). Also please post the image header or a link to the file itself if this doesn't reveal anything. Next, a general corruption like this could be a bug in the task and the message is a side effect. This could be due to using newer system libraries but relinking the tasks locally should normally fix that. Provided of course that you reset the package architecture before compiling so the new binaries ended up in the noao$bin.redhat directory and not the default (empty) noao$bin.generic. Check bin.generic to see if they're there, and bin.redhat to be sure the dates indicate the .e files were updated. The proper way to relink a package (assuming you've defined $iraf and $IRAFARCH) is with something like cl> cd noao$
cl> mkpkg -p noao redhat # reset the architecture
cl> mkpkg -p noao -p tables update # relink the packageNote that compilation on 64-bit systems is not yet supported. It may be that the library is fine but this is just some old bug that only shows itself with this version. In that case, please confirm that you were able to use this image prior to the update.Lastly, what were you doing when the crash happened? Does this occur right away, in response to some particular keystroke, only with this data, etc, etc. You can use the 'Forum Search' to find old message about the task that may shed some light, in the end backing out of the update may be the quickest way to a working system again as I don't have access to that particular configuration to test. Hope this helps.Cheers,
-Mike

 
Profile Email
 Quote
wkerzendorf
 03/21/2006 01:17AM  
+----
Newbie

Status: offline


Registered: 03/20/2006
Posts: 7
I mean glib-c, i upgraded to the newset glib-c and then iraf stopped working, i tried reinstalling it simply, i also tried to recompile it how you told me to. It doesnt work, i also upgraded the gtk+ can that affect iraf. Please help.
Thanks in advance
Wolfgang

 
Profile Email
 Quote
fitz
 03/21/2006 01:17AM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040
Wolfgang,Then, do you really mean glibc-2.3.5 (which I can find), or glibc-3.5 (which I cannot find)? Either way, please post more information such as a link to the data, you parameters, specifically what causes the error (e.g. crashes at startup or in response to some keystroke, if so, which one?). There isn't enough information yet to comment however the later glibc-2.3.6 is known to work. You might also check the old buglogs and mail archives for similar problem reports, the glibc update may be (partially) unrelated.-Mike

 
Profile Email
 Quote
   
Content generated in: 0.15 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 
dog allergies remedies cialis 20 mg chilblain remedies


Privacy Policy
Terms of Use

User Functions

Login