64-bit apall gives memory fwa corrupted panic error

[Paul Kerry]

Hi

One of our users has come across a problem when using certain parameters within noao.twodspec.apextract.apall on 64-bit linux.

When running...
apall WUma-010.fit weights=variance pfit=fit2d

at the subsequent
"Review extracted spectra from WUma-10? (yes):"
prompt an error occurs if entering yes or no...

PANIC in `/irafr/iraf/noao/bin.linux64/x_apextract.e' : Memory fwa has been corrupted

doing exactly the same thing with the same file on 32-bit linux correctly shows the extracted spectrum.

Cheers
Paul.

[Paul Kerry]

sorry - forget to mention that this is using version 2.15.1a

Cheers
Paul

[fitz]

Paul,

There are no known issues with APALL and no recent changes to indicate something was fixed, so we'll need more information in order to be able to reproduce the problem. Could you upload the data files used as well as the parameter setting (e.g. "dpar apall") to the anonftp at ftp://iraf.noao.edu/pub so we can have a look?

-Mike

[Paul Kerry]

done...

data file: WUma-010.fit
parameters file: pkerry_apall_params.txt

Cheers
Paul.

[fitz]

I can reproduce the error, but only on 64-bit linux. It appears to be some sort of memory corruption:

[Paul Kerry]

Thanks for looking at this for us - as I mentioned in the first post, it works perfectly under 32-bit linux: it's only under 64-bit linux that it has a problem...

Cheers
Paul.

[valdes]

Hi Paul,

I was able to reproduce this and track the source down. Below is the bug report. So it will be fixed in the next release. If you need something sooner let us know and we can provide a special patch to you.

Regards,
Frank Valdes

[Paul Kerry]

Thanks for fixing this - yes we could do with a patch if one is available please...

Cheers
Paul.

[fitz]

A patched linux64 binary for v2.15 is available from

ftp://iraf.noao.edu/iraf/v215/support/linux64/x_apextract.e

Let us know if you still have problems.

[Paul Kerry]

I've put in the patched version, but when using apall on the same file and setting the extraction weights to "variance", I now get...

PANIC in `/iraf/iraf/noao/bin.linux64/x_apextract.e': Salloc underflow


Cheers
Paul.

[fitz]

Paul,

Try getting the binary again, there was a code change that was overlooked that would explain the error. Sorry for the inconvenience.

-Mike

[Paul Kerry]

Thanks Mike - I've put in the new binary, but there is now another problem

apextract> apall
List of input images: WUma-010.fit
Find apertures for WUma-010? (yes):
Number of apertures to be found automatically: 1
Resize apertures for WUma-010? (yes):
Edit apertures for WUma-010? (yes):
ERROR: segmentation violation
called as: `apall ()'


at which point the graphics window should appear and doesn't and then I get kicked back to the "apextract>" prompt. It doesn't seem to make any difference if I change any apall parameters or if I run from a clean directory.


Cheers
Paul.

[valdes]

Hi Paul,

The fixes I made work on your data with linux64 in the various ways you indicate. So please get the file:

ftp://iraf.noao.edu/iraf/v215/support/linux64/x_apextract.eFV

and install it the usual place renaming it to the usual name (i.e. x_apextract.e). This binary is the one I built on a different linux64 platform and have not had a problem. Please let us know whether it works or not. If not, just to be sure, return the result of

[Paul Kerry]

that works perfectly - thanks for the fix...

Paul.

[FSBoyden]

Hi

I updated from V2.15 to V2.16 last week. Since then I get the same kind of error as described below for my x64 system. Sometimes the PANIC turns up, but mostly it only gives the segmentation violation. The few times that the PANIC protocol did show and displayed a back-trace, it seemed that it originates in x_images.e.... ....which seems right because sections is a subtask of images->imutil->sections.

Could you please have a look, because I use the sections task in a lot of in-house scripts.

Thank U
Regards
Pat