Update of bug #28897 (project gsl):
Status: None => Need Info
_______________________________________________________
Follow-up Comment #3:
The SEGVs seem to be due to the ambiguity between pointer arguments and
arrays. For example in the following code f_in and f_out should be arrays of
length 256 (the first argument "n" of the gsl_dht_new(n,nu,xmax) call). How
does your tool handle this?
gsl_dht.h, libgsl.so.0.14.0
[] gsl_dht_apply (gsl_dht const* t, double* f_in, double* f_out)
#include <stdlib.h>
#include <gsl_dht.h>
int main(int argc, char *argv[])
{
gsl_dht* t = gsl_dht_new(256, 1.5, 2.5);
double f_in = 3.5;
double f_out = 4.5;
gsl_dht_apply(t, &f_in, &f_out); //target call
return 0;
}
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?28897>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gsl mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gsl
