segmentation violation with txdump

Polly wrote on Feb 11, 2010

Hi I have an other problem already:

I'm using pyraf on OS X 10.5.8 with bash. When I try to use the txdump routine it always gives me the error:

ERROR (501, "segmentation violation")

What went wrong? I saw similar problem in the Forum already but not exaclty the same. I'm sorry if this question has already been asked but I really looked and didn't find this special combination.

Thank you.
Nora

PS: tdump works by the way!

---

Mike Fitzpatrick wrote on Feb 11, 2010

A 'segmentation violation' is a generic memory error message: It can either mean a coding error in the task or perhaps some combination of parameters or corruption in the data is not being caught properly.

There are no known issues with the task, if you could post your parameters (e.g. "cl> dpar txdump") and the input file being used it should be straightforward to track down if it can be duplicated. You can also upload these files to the anonftp archive at ftp://iraf.noao.edu/pub

-Mike

---

Polly wrote on Feb 11, 2010

Thank you Mike! I solved the problem by writing a python script to read the column I needed. I think it was a problem of the format of the table since it worked fine with other tables produced with iraf.

Nora

---

Mike Fitzpatrick wrote on Feb 11, 2010

Still, could you upload the parameters and data to ftp://iraf.noao.edu/pub so we can fix the problem for the next release?

-Mike

---

Polly wrote on Feb 11, 2010

Ok I did. It's the table corr.txt. The paramters were just

txdump corr.txt "SHIFT" yes

Nora

---

Last post on Feb 11, 2010