That's exactly what I did. The first gsl_matrix_free(b) was a valid instruction and didnot give out a segmentation fault error. However, the segmentation fault error was generated by the gsl_matrix_free(b) inside the try block.
Can anyone help me sort this out? Thanks, Adarsh > use directly this: > > try{ > gsl_matrix_free(b); > } > catch (const char *s){ > // i interpret this as: "do not take any action" > } > > cause you cannot free what you have ever freed before by the first : > gsl_matrix_free(b); > > Regards > > > > 2006/6/10, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: >> >> Hey All: >> >> Is there a way we can avoid Segmentation fault error when we try to free >> a >> gsl_matrix that was never allocated, or that has already been freed? I >> tried the following but didn't help: >> >> gsl_matrix_free(b); >> >> try{ >> gsl_matrix_free(b); >> } >> catch (const char *s){ >> // i interpret this as: "do not take any action" >> } >> >> >> Thanks, >> Adarsh >> >> >> >> _______________________________________________ >> Help-gsl mailing list >> Help-gsl@gnu.org >> http://lists.gnu.org/mailman/listinfo/help-gsl >> > > > > -- > Benamar BERRABAH > Master Student > LIPN Laboratoire d'Informatique de Paris Nord > Institut Galilée - Univesité Paris 13 > 99, Av Jean Baptiste Clément > 95430 Villetaneuse > FRANCE > Tel: 0149403213 > Mob: 061766947 > Mail: [EMAIL PROTECTED] > _______________________________________________ Help-gsl mailing list Help-gsl@gnu.org http://lists.gnu.org/mailman/listinfo/help-gsl