Dear Sir/Madam
I couldn't use the following macro to prepare waveforms for inversion in the
search of fault plane solution.
r %base%BHZ* %base%BHE* %base%BHN*
SAC exist with message "segmentation fault"
I think this problem arouse on account of small value of RAM (128 MB). Could
you please write the real cause and how to fix it?
Regards,
Sudhir
Tease your brain--play Clink! Win cool prizes!
http://club.live.com/clink.aspx?icid=clink_hotmailtextlink2
I couldn't use the following macro to prepare waveforms for inversion in the
search of fault plane solution.
r %base%BHZ* %base%BHE* %base%BHN*
SAC exist with message "segmentation fault"
I think this problem arouse on account of small value of RAM (128 MB). Could
you please write the real cause and how to fix it?
Regards,
Sudhir
From: sac-help-request<at>iris.washington.edu_________________________________________________________________
Reply-To: sac-help<at>iris.washington.edu
To: sac-help<at>iris.washington.edu
Subject: sac-help Digest, Vol 26, Issue 2
Date: Fri, 3 Aug 2007 12:01:48 -0700 (PDT)
Send sac-help mailing list submissions to
sac-help<at>iris.washington.edu
To subscribe or unsubscribe via the World Wide Web, visit
http://www.iris.washington.edu/mailman/listinfo/sac-help
or, via email, send a message with subject or body 'help' to
sac-help-request<at>iris.washington.edu
You can reach the person managing the list at
sac-help-owner<at>iris.washington.edu
When replying, please edit your Subject line so it is more specific
than "Re: Contents of sac-help digest..."
Today's Topics:
1. Bug Report rsac1/rsac2 in sacio (Brian Savage)
----------------------------------------------------------------------
Message: 1
Date: Fri, 3 Aug 2007 10:40:37 -0400
From: Brian Savage <savage<at>uri.edu>
Subject: [SAC-HELP] Bug Report rsac1/rsac2 in sacio
To: SAC HELP <sac-help<at>iris.washington.edu>
Message-ID: <9617BFAB-73A0-4C83-B906-184FDBBC9EA2<at>uri.edu>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
SAC Users
A bug had been discovered when using rsac1() from the sacio library.
This bug also affects rsac2() as the function logic is essentially
the same.
Description:
If the sac file being read contains more data points than expected an
error value is not returned as it should be. A error return value
(variable nerr) of -803 should be returned but is this value is set
to 0 if no other errors are encountered. The number of data points
read in (variable nlen) will be returned and set to the maximum
number allowed (variable max).
Workaround:
If the number of data points rsac1 (or rsac2) returns as read
(variable nlen) is equal to the maximum number allowed (variable max)
there is a possibility that the requested file to be read contains
more points. Increase the size of the array and reread the file.
Fix: (Either 1 or 2)
1) This bug will be fixed in the next release of SAC
2) Request an updated rsac1() and rsac2() and recompile the sacio
library from source.
Cheers,
Brian Savage
------------------------------
_______________________________________________
sac-help mailing list
sac-help<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/sac-help
End of sac-help Digest, Vol 26, Issue 2
***************************************
Tease your brain--play Clink! Win cool prizes!
http://club.live.com/clink.aspx?icid=clink_hotmailtextlink2
-
There are several things that cause this error message.
Maybe your data has the wrong endianness? This is not a problem in the
current version of SAC, but it was an issue in "veteran" versions.
Which one are you using?
Andreas
On 8/15/07, Sudhir Rajaure <srajaure<at>hotmail.com> wrote:
r %base%BHZ* %base%BHE* %base%BHN*
SAC exist with message "segmentation fault"