Flawfinder version 2.0.10, (C) 2001-2019 David A. Wheeler.
Number of rules (primarily dangerous function names) in C/C++ ruleset: 223
Examining data/armadillo-9.900.1+dfsg/examples/example1.cpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/BaseCube_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/BaseCube_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/Base_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/Base_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/CubeToMatOp_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/CubeToMatOp_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/GenCube_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/GenCube_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/GenSpecialiser.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/Gen_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/Gen_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/GlueCube_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/GlueCube_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/Glue_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/Glue_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/OpCube_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/OpCube_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/Op_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/Op_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/Proxy.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/ProxyCube.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SizeCube_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SizeCube_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SizeMat_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SizeMat_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpBase_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpBase_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpCol_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpCol_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpGlue_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpGlue_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_iterators_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpOp_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpOp_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpProxy.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpRow_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpRow_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_iterators_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpToDOp_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpToDOp_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpValProxy_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpValProxy_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/access.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_cmath.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_config.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_forward.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_ostream_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_ostream_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_rel_comparators.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_rng.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_rng_cxx11.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_rng_cxx98.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_static_check.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_str.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_version.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/arrayops_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/arrayops_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/band_helper.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/compiler_extra.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/compiler_setup.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/compiler_setup_post.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/cond_rel_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/cond_rel_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/config.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/constants.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/constants_old.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/csv_name.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/debug.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/def_arpack.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/def_atlas.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/def_blas.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/def_hdf5.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/def_lapack.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/def_superlu.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/diagmat_proxy.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/diagview_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/diagview_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/distr_param.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/eGlueCube_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/eGlueCube_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/eGlue_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/eGlue_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/eOpCube_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/eOpCube_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/eOp_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/eOp_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/eglue_core_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/eglue_core_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/eop_aux.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/eop_core_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/eop_core_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fft_engine.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_accu.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_all.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_any.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_approx_equal.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_as_scalar.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_chi2rnd.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_chol.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_clamp.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_cond.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_conv.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_conv_to.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_cor.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_cov.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_cross.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_cumprod.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_cumsum.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_det.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_diagmat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_diagvec.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_diff.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_dot.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_eig_gen.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_eig_pair.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_eig_sym.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_eigs_gen.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_eigs_sym.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_elem.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_eps.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_expmat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_eye.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_fft.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_fft2.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_find.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_find_unique.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_flip.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_hess.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_hist.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_histc.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_index_max.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_index_min.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_inplace_strans.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_inplace_trans.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_interp1.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_interp2.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_intersect.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_inv.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_join.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_kmeans.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_kron.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_log_det.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_log_normpdf.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_logmat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_lu.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_max.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_mean.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_median.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_min.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_misc.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_mvnrnd.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_n_unique.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_nonzeros.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_norm.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_normalise.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_normcdf.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_normpdf.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_numel.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_ones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_orth_null.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_pinv.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_polyfit.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_polyval.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_powmat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_princomp.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_prod.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_qr.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_quantile.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_qz.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_randg.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_randi.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_randn.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_randperm.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_randu.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_range.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_rank.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_regspace.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_repelem.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_repmat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_reshape.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_resize.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_reverse.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_roots.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_schur.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_shift.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_shuffle.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_size.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_solve.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_sort.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_sort_index.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_speye.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_spones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_sprandn.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_sprandu.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_spsolve.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_sqrtmat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_stddev.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_strans.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_sum.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_svd.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_svds.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_syl_lyap.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_symmat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_toeplitz.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_trace.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_trans.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_trapz.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_trig.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_trimat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_trimat_ind.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_trunc_exp.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_trunc_log.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_unique.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_var.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_vectorise.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_wishrnd.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_zeros.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_affmul_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_affmul_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_atan2_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_atan2_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_conv_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_conv_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_cor_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_cor_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_cov_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_cov_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_cross_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_cross_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_hist_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_hist_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_histc_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_histc_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_hypot_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_hypot_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_intersect_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_intersect_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_join_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_join_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_kron_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_kron_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_max_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_max_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_min_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_min_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_mixed_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_mixed_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_mvnrnd_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_mvnrnd_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_polyfit_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_polyfit_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_polyval_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_polyval_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_quantile_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_quantile_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_relational_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_relational_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_solve_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_solve_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_times_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_times_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_toeplitz_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_toeplitz_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_trapz_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/glue_trapz_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_misc_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_misc_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/hdf5_misc.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/hdf5_name.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/include_atlas.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/include_hdf5.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/include_superlu.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/injector_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/injector_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/memory.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/mp_misc.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/mtGlueCube_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/mtGlueCube_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/mtGlue_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/mtGlue_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/mtOpCube_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/mtOpCube_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/mtOp_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/mtOp_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/mtSpGlue_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/mtSpGlue_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/mtSpOp_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/mtSpOp_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/mul_gemm.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/mul_gemm_mixed.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/mul_gemv.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/mul_herk.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/mul_syrk.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_DenseGenMatProd_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_DenseGenMatProd_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_DoubleShiftQR_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_DoubleShiftQR_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_EigsSelect.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_GenEigsSolver_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_GenEigsSolver_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_SortEigenvalue.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_SparseGenMatProd_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_SparseGenMatProd_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_SymEigsSolver_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_SymEigsSolver_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_TridiagEigen_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_TridiagEigen_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_UpperHessenbergEigen_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_UpperHessenbergEigen_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_UpperHessenbergQR_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_UpperHessenbergQR_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/newarp_cx_attrib.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_all_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_all_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_any_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_any_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_chi2rnd_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_chi2rnd_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_chol_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_chol_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_clamp_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_clamp_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_cond_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_cond_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_cor_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_cor_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_cov_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_cov_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_cumprod_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_cumprod_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_cumsum_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_cumsum_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_cx_scalar_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_cx_scalar_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_diagmat_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_diagmat_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_diagvec_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_diagvec_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_diff_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_diff_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_dot_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_dot_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_dotext_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_dotext_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_expmat_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_expmat_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_fft_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_fft_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_find_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_find_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_find_unique_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_find_unique_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_flip_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_flip_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_hist_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_hist_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_htrans_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_htrans_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_index_max_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_index_max_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_index_min_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_index_min_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_inv_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_inv_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_logmat_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_logmat_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_max_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_max_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_mean_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_mean_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_median_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_median_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_min_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_min_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_misc_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_misc_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_nonzeros_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_nonzeros_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_norm_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_norm_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_normalise_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_normalise_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_orth_null_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_orth_null_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_pinv_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_pinv_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_powmat_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_powmat_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_princomp_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_princomp_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_prod_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_prod_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_range_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_range_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_relational_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_relational_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_repelem_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_repelem_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_repmat_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_repmat_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_reshape_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_reshape_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_resize_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_resize_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_reverse_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_reverse_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_roots_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_roots_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_shift_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_shift_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_shuffle_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_shuffle_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_sort_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_sort_index_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_sort_index_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_sort_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_sp_minus_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_sp_minus_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_sp_plus_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_sp_plus_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_sqrtmat_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_sqrtmat_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_stddev_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_stddev_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_strans_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_strans_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_sum_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_sum_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_symmat_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_symmat_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_toeplitz_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_toeplitz_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_trimat_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_trimat_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_unique_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_unique_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_var_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_var_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_vectorise_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_vectorise_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_wishrnd_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_wishrnd_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/operator_cube_div.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/operator_cube_minus.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/operator_cube_plus.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/operator_cube_relational.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/operator_cube_schur.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/operator_cube_times.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/operator_div.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/operator_minus.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/operator_ostream.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/operator_plus.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/operator_relational.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/operator_schur.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/operator_times.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/podarray_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/podarray_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/promote_type.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/restrictors.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/running_stat_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/running_stat_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/running_stat_vec_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/running_stat_vec_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/span.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spdiagview_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spdiagview_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_elem_helper_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_elem_helper_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_join_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_join_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_kron_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_kron_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_max_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_max_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_min_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_min_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_minus_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_minus_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_plus_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_plus_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_relational_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_relational_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_times_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_times_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_diagmat_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_diagmat_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_htrans_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_htrans_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_max_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_max_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_mean_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_mean_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_min_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_min_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_misc_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_misc_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_normalise_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_normalise_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_repmat_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_repmat_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_reverse_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_reverse_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_strans_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_strans_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_sum_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_sum_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_symmat_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_symmat_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_trimat_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_trimat_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_var_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_var_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_vectorise_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_vectorise_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/strip.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_each_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_each_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_slices_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_slices_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_each_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_each_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_elem1_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_elem1_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_elem2_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_elem2_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_field_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_field_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/sympd_helper.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/traits.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/translate_arpack.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/translate_atlas.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/translate_blas.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/translate_lapack.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/translate_superlu.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/trimat_helper.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/typedef_elem.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/typedef_elem_check.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/typedef_mat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/typedef_mat_fixed.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/unwrap.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/unwrap_cube.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/unwrap_spmat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/upgrade_val.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/wall_clock_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/wall_clock_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/xtrans_mat_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/xtrans_mat_meat.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/xvec_htrans_bones.hpp
Examining data/armadillo-9.900.1+dfsg/include/armadillo_bits/xvec_htrans_meat.hpp
Examining data/armadillo-9.900.1+dfsg/mex_interface/armaMex.hpp
Examining data/armadillo-9.900.1+dfsg/mex_interface/armaMex_demo.cpp
Examining data/armadillo-9.900.1+dfsg/mex_interface/readMatTest.cpp
Examining data/armadillo-9.900.1+dfsg/smoke_test/smoke_test.cpp
Examining data/armadillo-9.900.1+dfsg/src/wrapper1.cpp
Examining data/armadillo-9.900.1+dfsg/src/wrapper2.cpp
Examining data/armadillo-9.900.1+dfsg/tests/attributes.cpp
Examining data/armadillo-9.900.1+dfsg/tests/bounds.cpp
Examining data/armadillo-9.900.1+dfsg/tests/catch.hpp
Examining data/armadillo-9.900.1+dfsg/tests/decomp_eig_gen.cpp
Examining data/armadillo-9.900.1+dfsg/tests/decomp_eig_pair.cpp
Examining data/armadillo-9.900.1+dfsg/tests/decomp_eig_sym.cpp
Examining data/armadillo-9.900.1+dfsg/tests/expr_elem.cpp
Examining data/armadillo-9.900.1+dfsg/tests/expr_misc.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_abs.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_accu.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_all.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_any.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_as_scalar.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_clamp.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_cond.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_conj.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_conv.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_conv_to.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_cor.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_cov.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_cross.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_cumprod.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_cumsum.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_det.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_diagmat.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_diagvec.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_diff.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_dot.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_eigs_gen.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_eigs_sym.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_eps.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_expmat.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_find.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_find_finite.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_find_nonfinite.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_find_unique.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_flip.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_hess.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_interp1.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_intersect.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_is_finite.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_max.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_mean.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_min.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_princomp.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_spsolve.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_sum.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_symmat.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_trace.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_trans.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_var.cpp
Examining data/armadillo-9.900.1+dfsg/tests/fn_vectorise.cpp
Examining data/armadillo-9.900.1+dfsg/tests/gen_linspace.cpp
Examining data/armadillo-9.900.1+dfsg/tests/gen_ones.cpp
Examining data/armadillo-9.900.1+dfsg/tests/gen_randu.cpp
Examining data/armadillo-9.900.1+dfsg/tests/gen_zeros.cpp
Examining data/armadillo-9.900.1+dfsg/tests/gmm.cpp
Examining data/armadillo-9.900.1+dfsg/tests/hdf5.cpp
Examining data/armadillo-9.900.1+dfsg/tests/init_auxmem.cpp
Examining data/armadillo-9.900.1+dfsg/tests/init_fill.cpp
Examining data/armadillo-9.900.1+dfsg/tests/init_misc.cpp
Examining data/armadillo-9.900.1+dfsg/tests/instantiation.cpp
Examining data/armadillo-9.900.1+dfsg/tests/main.cpp
Examining data/armadillo-9.900.1+dfsg/tests/mat_minus.cpp
Examining data/armadillo-9.900.1+dfsg/tests/mat_mul_cx.cpp
Examining data/armadillo-9.900.1+dfsg/tests/mat_mul_real.cpp
Examining data/armadillo-9.900.1+dfsg/tests/mat_neg.cpp
Examining data/armadillo-9.900.1+dfsg/tests/mat_plus.cpp
Examining data/armadillo-9.900.1+dfsg/tests/spcol.cpp
Examining data/armadillo-9.900.1+dfsg/tests/spmat.cpp
Examining data/armadillo-9.900.1+dfsg/tests/sprow.cpp
Examining data/armadillo-9.900.1+dfsg/tests/spsubview.cpp

FINAL RESULTS:

data/armadillo-9.900.1+dfsg/include/armadillo_bits/BaseCube_meat.hpp:187:26:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      const T val_real = access::tmp_real(val);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/BaseCube_meat.hpp:188:26:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      const T val_imag = access::tmp_imag(val);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Base_meat.hpp:316:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    if( access::tmp_imag(A_col[j]) != T(0) )  { return false; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Base_meat.hpp:333:22:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      if(A_col[i] != access::alt_conj(*A_row))  { return false; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Base_meat.hpp:411:26:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      const T val_real = access::tmp_real(val);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Base_meat.hpp:412:26:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      const T val_imag = access::tmp_imag(val);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:145:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(tmp.n_rows) = tmp.n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:146:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(tmp.n_cols) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:178:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(tmp.n_rows) = tmp.n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:179:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(tmp.n_cols) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:249:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(tmp.n_rows) = tmp.n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:250:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(tmp.n_cols) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:266:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Mat<eT>::n_rows) = X.n_rows;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:267:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Mat<eT>::n_cols) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:268:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Mat<eT>::n_elem) = X.n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:272:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(Mat<eT>::mem_state) = X.mem_state;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:273:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(Mat<eT>::mem)       = X.mem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:275:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.n_rows)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:276:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.n_cols)    = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:277:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.n_elem)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:278:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.mem_state) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:279:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.mem)       = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:289:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(X.n_rows) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:290:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(X.n_cols) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:291:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(X.n_elem) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:292:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(X.mem)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:310:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.n_rows) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:311:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.n_cols) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:312:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.n_elem) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:313:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.mem)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:415:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(Mat<eT>::vec_state) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:428:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(Mat<eT>::vec_state) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:444:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(Mat<eT>::vec_state) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:458:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(Mat<eT>::vec_state) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:486:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(Mat<eT>::vec_state) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:1013:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw(Mat<eT>::mem[i]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Col_meat.hpp:1035:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( Mat<eT>::mem[in_row] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:31:22:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    memory::release( access::rw(mem) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:37:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(mem)      = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:38:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(mat_ptrs) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:223:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(mem) = NULL;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:228:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(mem) = mem_local;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:234:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(mem) = memory::acquire<eT>(n_elem);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:287:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_rows)       = in_n_rows;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:288:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_cols)       = in_n_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:289:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_elem_slice) = in_n_rows*in_n_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:290:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_slices)     = in_n_slices;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:307:28:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          memory::release( access::rw(mem) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:312:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          access::rw(mem) = NULL;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:317:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          access::rw(mem) = mem_local;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:330:26:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        memory::release( access::rw(mem) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:336:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(mem) = mem_local;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:341:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(mem) = memory::acquire<eT>(new_n_elem);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:344:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(mem_state) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:347:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_rows)       = in_n_rows;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:348:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_cols)       = in_n_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:349:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_elem_slice) = in_n_rows*in_n_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:350:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_slices)     = in_n_slices;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:351:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_elem)       = new_n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:434:46:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      if(mat_ptrs[uslice] != NULL)  { delete access::rw(mat_ptrs[uslice]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:455:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(mat_ptrs) = NULL;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:463:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(mat_ptrs) = const_cast< const Mat<eT>** >(mat_ptrs_local);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:467:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(mat_ptrs) = new(std::nothrow) const Mat<eT>*[n_slices];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:492:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(mem[0]) = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:3223:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw(mem[i]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:3247:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw(mem[i]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:3271:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw(mem[i]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:3304:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw(mem[in_slice*n_elem_slice + in_col*n_rows + in_row]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:3337:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( mem[in_slice*n_elem_slice + in_col*n_rows + in_row] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:4959:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw(mem[0]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:4983:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw(mem[n_elem-1]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5014:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_rows),       access::rw(B.n_rows)       );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5014:44:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_rows),       access::rw(B.n_rows)       );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5015:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_cols),       access::rw(B.n_cols)       );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5015:44:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_cols),       access::rw(B.n_cols)       );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5016:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_elem_slice), access::rw(B.n_elem_slice) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5016:44:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_elem_slice), access::rw(B.n_elem_slice) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5017:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_slices),     access::rw(B.n_slices)     );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5017:44:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_slices),     access::rw(B.n_slices)     );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5018:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_elem),       access::rw(B.n_elem)       );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5018:44:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_elem),       access::rw(B.n_elem)       );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5019:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.mem),          access::rw(B.mem)          );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5019:44:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.mem),          access::rw(B.mem)          );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5030:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_rows),       access::rw(B.n_rows)       );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5030:44:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_rows),       access::rw(B.n_rows)       );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5031:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_cols),       access::rw(B.n_cols)       );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5031:44:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_cols),       access::rw(B.n_cols)       );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5032:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_elem_slice), access::rw(B.n_elem_slice) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5032:44:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_elem_slice), access::rw(B.n_elem_slice) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5033:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_slices),     access::rw(B.n_slices)     );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5033:44:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_slices),     access::rw(B.n_slices)     );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5034:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_elem),       access::rw(B.n_elem)       );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5034:44:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_elem),       access::rw(B.n_elem)       );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5086:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_rows)       = x.n_rows;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5087:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_cols)       = x.n_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5088:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_elem_slice) = x.n_elem_slice;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5089:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_slices)     = x_n_slices;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5090:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_elem)       = x.n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5091:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(mem_state)    = x.mem_state;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5092:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(mem)          = x.mem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5096:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(  mat_ptrs) = x.mat_ptrs;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5097:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(x.mat_ptrs) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5101:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(mat_ptrs) = const_cast< const Mat<eT>** >(mat_ptrs_local);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5110:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.n_rows)       = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5111:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.n_cols)       = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5112:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.n_elem_slice) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5113:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.n_slices)     = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5114:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.n_elem)       = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5115:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.mem_state)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5116:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.mem)          = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5141:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Cube<eT>::n_rows)       = fixed_n_rows;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5142:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Cube<eT>::n_cols)       = fixed_n_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5143:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Cube<eT>::n_elem_slice) = fixed_n_rows * fixed_n_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5144:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Cube<eT>::n_slices)     = fixed_n_slices;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5145:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Cube<eT>::n_elem)       = fixed_n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5146:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Cube<eT>::mem_state)    = 3;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5147:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Cube<eT>::mem)          = (fixed_n_elem   > Cube_prealloc::mem_n_elem)    ? mem_local_extra      : mem_local;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5148:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Cube<eT>::mat_ptrs)     = const_cast< const Mat<eT>** >( \
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5155:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Cube<eT>::n_rows)       = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5156:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Cube<eT>::n_cols)       = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5157:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Cube<eT>::n_elem_slice) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5158:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Cube<eT>::n_slices)     = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5159:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Cube<eT>::n_elem)       = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5160:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Cube<eT>::mem_state)    = 3;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5161:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Cube<eT>::mem)          = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Cube_meat.hpp:5162:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Cube<eT>::mat_ptrs)     = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:109:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_rows) = x.n_rows;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:110:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_cols) = x.n_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:111:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_elem) = x.n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:190:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.n_rows)  = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:191:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.n_cols)  = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:192:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.n_elem)  = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:193:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.map_ptr) = NULL;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:209:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_rows)  = x.n_rows;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:210:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_cols)  = x.n_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:211:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_elem)  = x.n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:212:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(map_ptr) = x.map_ptr;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:214:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.n_rows)  = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:215:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.n_cols)  = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:216:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.n_elem)  = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:217:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.map_ptr) = NULL;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:231:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_rows) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:232:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_cols) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:233:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_elem) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:799:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_rows) = in_n_rows;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:800:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_cols) = in_n_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:801:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_elem) = new_n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:903:13:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return T( access::tmp_real( const_parent.operator[](index) ) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:919:13:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return T( access::tmp_imag( const_parent.operator[](index) ) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1158:13:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return T( access::tmp_real( const_s_parent.get_value(row,col) ) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1174:13:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return T( access::tmp_imag( const_s_parent.get_value(row,col) ) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1439:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(s_parent.n_nonzero) = m_parent.get_n_nonzero();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1470:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(s_parent.n_nonzero) = m_parent.get_n_nonzero();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1501:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(s_parent.n_nonzero) = m_parent.get_n_nonzero();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1544:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(s_parent.n_nonzero) = m_parent.get_n_nonzero();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1559:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          access::rw(s_parent.n_nonzero) = m_parent.get_n_nonzero();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1598:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(s_parent.n_nonzero) = m_parent.get_n_nonzero();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1613:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          access::rw(s_parent.n_nonzero) = m_parent.get_n_nonzero();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1630:26:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  : SpMat_MapMat_val<eT>(access::rw(in_sv_parent.m), in_m_parent, in_row, in_col)
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1663:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(sv_parent.m.n_nonzero > old_n_nonzero)  { access::rw(sv_parent.n_nonzero)++; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1664:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(sv_parent.m.n_nonzero < old_n_nonzero)  { access::rw(sv_parent.n_nonzero)--; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1682:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(sv_parent.m.n_nonzero > old_n_nonzero)  { access::rw(sv_parent.n_nonzero)++; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1683:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(sv_parent.m.n_nonzero < old_n_nonzero)  { access::rw(sv_parent.n_nonzero)--; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1701:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(sv_parent.m.n_nonzero > old_n_nonzero)  { access::rw(sv_parent.n_nonzero)++; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1702:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(sv_parent.m.n_nonzero < old_n_nonzero)  { access::rw(sv_parent.n_nonzero)--; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1720:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(sv_parent.m.n_nonzero > old_n_nonzero)  { access::rw(sv_parent.n_nonzero)++; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1721:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(sv_parent.m.n_nonzero < old_n_nonzero)  { access::rw(sv_parent.n_nonzero)--; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1739:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(sv_parent.m.n_nonzero > old_n_nonzero)  { access::rw(sv_parent.n_nonzero)++; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1740:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(sv_parent.m.n_nonzero < old_n_nonzero)  { access::rw(sv_parent.n_nonzero)--; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1758:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(sv_parent.m.n_nonzero > old_n_nonzero)  { access::rw(sv_parent.n_nonzero)++; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1759:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(sv_parent.m.n_nonzero < old_n_nonzero)  { access::rw(sv_parent.n_nonzero)--; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1778:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(sv_parent.m.n_nonzero > old_n_nonzero)  { access::rw(sv_parent.n_nonzero)++; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1779:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(sv_parent.m.n_nonzero < old_n_nonzero)  { access::rw(sv_parent.n_nonzero)--; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1797:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(sv_parent.m.n_nonzero > old_n_nonzero)  { access::rw(sv_parent.n_nonzero)++; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1798:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(sv_parent.m.n_nonzero < old_n_nonzero)  { access::rw(sv_parent.n_nonzero)--; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1817:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(sv_parent.m.n_nonzero > old_n_nonzero)  { access::rw(sv_parent.n_nonzero)++; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/MapMat_meat.hpp:1818:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(sv_parent.m.n_nonzero < old_n_nonzero)  { access::rw(sv_parent.n_nonzero)--; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:29:22:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    memory::release( access::rw(mem) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:33:29:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(arma_config::debug)  { access::rw(mem) = 0; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:209:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(mem) = NULL;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:214:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(mem) = mem_local;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:220:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(mem) = memory::acquire<eT>(n_elem);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:285:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_rows) = in_n_rows;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:286:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_cols) = in_n_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:299:28:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          memory::release( access::rw(mem) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:304:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          access::rw(mem) = NULL;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:309:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          access::rw(mem) = mem_local;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:322:26:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        memory::release( access::rw(mem) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:328:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(mem) = mem_local;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:333:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(mem) = memory::acquire<eT>(new_n_elem);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:336:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(mem_state) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:339:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_rows) = in_n_rows;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:340:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_cols) = in_n_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:341:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_elem) = new_n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:654:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(mem_state) = X.mem_state;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:655:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(mem)       = X.mem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:657:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.n_rows)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:658:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.n_cols)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:659:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.n_elem)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:660:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.mem_state) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:661:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.mem)       = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:671:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(X.n_rows) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:672:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(X.n_cols) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:673:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(X.n_elem) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:674:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(X.mem)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:692:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.n_rows) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:693:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.n_cols) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:694:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.n_elem) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:695:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.mem)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:715:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(mem[0]) = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1006:18:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      std::swap( access::rw(A.mem), access::rw(B.mem) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1006:37:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      std::swap( access::rw(A.mem), access::rw(B.mem) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1014:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(A.mem) = A_mem_local;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1015:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(B.mem) = B_mem_local;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1029:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(A.mem) = B.mem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1030:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(B.mem) = B_mem_local;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1040:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(B.mem) = A.mem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1041:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(A.mem) = A_mem_local;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1044:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_rows), access::rw(B.n_rows) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1044:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_rows), access::rw(B.n_rows) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1045:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_cols), access::rw(B.n_cols) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1045:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_cols), access::rw(B.n_cols) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1046:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_elem), access::rw(B.n_elem) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1046:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_elem), access::rw(B.n_elem) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1051:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_rows), access::rw(B.n_rows) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1051:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_rows), access::rw(B.n_rows) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1052:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_cols), access::rw(B.n_cols) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1052:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_cols), access::rw(B.n_cols) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1131:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_rows)    = x_n_rows;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1132:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_cols)    = x_n_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1133:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_elem)    = x_n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1134:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(mem_state) = x_mem_state;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1135:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(mem)       = x.mem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1137:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.n_rows)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1138:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.n_cols)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1139:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.n_elem)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1140:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.mem_state) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1141:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(x.mem)       = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1185:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(n_rows)    = alt_n_rows;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1186:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(n_cols)    = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1187:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(n_elem)    = alt_n_rows;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1188:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(mem_state) = x_mem_state;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1189:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(mem)       = x.mem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1191:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(x.n_rows)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1192:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(x.n_cols)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1193:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(x.n_elem)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1194:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(x.mem_state) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:1195:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(x.mem)       = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:2649:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(mem[cur_loc]) *= (*it);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:4133:18:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      std::swap( access::rw(mem[pos1]), access::rw(mem[pos2]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:4133:41:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      std::swap( access::rw(mem[pos1]), access::rw(mem[pos2]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:5861:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw(mem[ii]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:5885:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw(mem[ii]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:5909:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw(mem[ii]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:5934:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw(mem[in_row + in_col*n_rows]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:5959:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( mem[in_row + in_col*n_rows] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:6422:12:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return & access::rw(mem[in_col*n_rows]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:9035:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw(mem[0]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:9059:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw(mem[n_elem-1]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Mat_meat.hpp:9555:12:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return & access::rw(mem_actual[in_col*fixed_n_rows]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:145:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(tmp.n_rows) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:146:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(tmp.n_cols) = tmp.n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:178:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(tmp.n_rows) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:179:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(tmp.n_cols) = tmp.n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:249:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(tmp.n_rows) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:250:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(tmp.n_cols) = tmp.n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:266:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Mat<eT>::n_rows) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:267:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Mat<eT>::n_cols) = X.n_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:268:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(Mat<eT>::n_elem) = X.n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:272:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(Mat<eT>::mem_state) = X.mem_state;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:273:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(Mat<eT>::mem)       = X.mem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:275:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.n_rows)    = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:276:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.n_cols)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:277:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.n_elem)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:278:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.mem_state) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:279:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.mem)       = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:289:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(X.n_rows) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:290:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(X.n_cols) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:291:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(X.n_elem) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:292:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(X.mem)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:310:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.n_rows) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:311:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.n_cols) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:312:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.n_elem) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:313:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(X.mem)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:415:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(Mat<eT>::vec_state) = 2;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:428:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(Mat<eT>::vec_state) = 2;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:444:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(Mat<eT>::vec_state) = 2;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:458:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(Mat<eT>::vec_state) = 2;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:486:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(Mat<eT>::vec_state) = 2;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:1013:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw(Mat<eT>::mem[i]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/Row_meat.hpp:1035:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( Mat<eT>::mem[in_col] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpBase_meat.hpp:435:26:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      const T val_real = access::tmp_real(val);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpBase_meat.hpp:436:26:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      const T val_imag = access::tmp_imag(val);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpCol_meat.hpp:318:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(SpMat<eT>::values) = new_values;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpCol_meat.hpp:319:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(SpMat<eT>::row_indices) = new_row_indices;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpCol_meat.hpp:321:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(SpMat<eT>::n_nonzero) -= elem_diff;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpCol_meat.hpp:322:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(SpMat<eT>::col_ptrs[1]) -= elem_diff;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpCol_meat.hpp:325:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(SpMat<eT>::n_rows) -= diff;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpCol_meat.hpp:326:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(SpMat<eT>::n_elem) -= diff;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_iterators_meat.hpp:323:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(*iterator_base::M),
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_iterators_meat.hpp:324:6:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    &access::rw(iterator_base::M->values[iterator_base::internal_pos]));
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_iterators_meat.hpp:935:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(*iterator_base::M),
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_iterators_meat.hpp:936:8:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      &access::rw(iterator_base::M->values[const_row_iterator::actual_pos]));
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:52:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(values     )  { memory::release(access::rw(values));      }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:53:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(row_indices)  { memory::release(access::rw(row_indices)); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:54:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(col_ptrs   )  { memory::release(access::rw(col_ptrs));    }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:138:39:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(x.row_indices)  { arrayops::copy(access::rwp(row_indices), x.row_indices, x.n_nonzero + 1); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:139:39:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(x.col_ptrs   )  { arrayops::copy(access::rwp(col_ptrs),    x.col_ptrs,    x.n_cols    + 1); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:578:18:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::copy(access::rwp(row_indices), rowind.memptr(), rowind.n_elem );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:579:18:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::copy(access::rwp(col_ptrs),    colptr.memptr(), colptr.n_elem );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:580:18:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::copy(access::rwp(values),      vals.memptr(),   vals.n_elem   );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:583:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(col_ptrs[n_cols + 1]) = std::numeric_limits<uword>::max();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:604:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(values[0]) = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:605:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(row_indices[0]) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:606:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(col_ptrs[1]) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:632:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    eT* vals = access::rwp(values);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:671:14:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  eT* vals = access::rwp(values);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:883:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(values[cur_pos]) = std::complex<T>((T) *x_it, (T) *y_it);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:884:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(row_indices[cur_pos]) = x_it.row();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:885:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      ++access::rw(col_ptrs[x_it.col() + 1]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:894:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(values[cur_pos]) = std::complex<T>((T) *x_it, T(0));
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:895:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(row_indices[cur_pos]) = x_it.row();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:896:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        ++access::rw(col_ptrs[x_it.col() + 1]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:902:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(values[cur_pos]) = std::complex<T>(T(0), (T) *y_it);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:903:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(row_indices[cur_pos]) = y_it.row();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:904:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        ++access::rw(col_ptrs[y_it.col() + 1]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:916:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(col_ptrs[c]) += col_ptrs[c - 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:999:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(values[n])      = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1000:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(row_indices[n]) = i;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1001:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(col_ptrs[j + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1009:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(col_ptrs[c]) += col_ptrs[c - 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1115:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(z.values[cur_pos]) = partial_sums[i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1116:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(z.row_indices[cur_pos]) = i;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1117:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        ++access::rw(z.col_ptrs[lcol + 1]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1128:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(z.col_ptrs[c]) += z.col_ptrs[c - 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1208:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(tmp.values[cur_pos]) = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1209:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(tmp.row_indices[cur_pos]) = c_it.row();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1210:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      ++access::rw(tmp.col_ptrs[c_it.col() + 1]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1220:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(tmp.col_ptrs[c]) += tmp.col_ptrs[c - 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1273:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(values[count])      = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1274:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(row_indices[count]) = i;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1275:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(col_ptrs[i + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1283:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(col_ptrs[i]) += col_ptrs[i - 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1287:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(         n_nonzero) = count;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1288:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(     values[count]) = eT(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1289:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(row_indices[count]) = uword(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1430:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(row_indices[count]) = m_it.row();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1431:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(values[count]) = (*m_it);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1432:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        ++access::rw(col_ptrs[m_it_col_adjusted + 1]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1448:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(row_indices[it_pos]) = it.row();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1449:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(values[it_pos]) = (*it);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1450:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        ++access::rw(col_ptrs[it.col() + 1]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:1458:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(col_ptrs[c]) += col_ptrs[c - 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:2874:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(values[loc1]) = values[loc2];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:2875:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(values[loc2]) = tmp;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:2885:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(values[loc1]) = values[loc1 + 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:2886:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(values[loc1 + 1]) = tmp;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:2889:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(row_indices[loc1]) = row_indices[loc1 + 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:2890:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(row_indices[loc1 + 1]) = tmp_index;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:2896:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(row_indices[loc1]) = in_row2;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:2907:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(values[loc2]) = values[loc2 - 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:2908:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(values[loc2 - 1]) = tmp;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:2911:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(row_indices[loc2]) = row_indices[loc2 - 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:2912:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(row_indices[loc2 - 1]) = tmp_index;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:2918:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(row_indices[loc2]) = in_row1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:3017:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(newmat.col_ptrs[i]) = col_ptrs[i] - col_ptrs[i - 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:3037:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      --access::rw(newmat.col_ptrs[lcol + 1]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:3045:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(newmat.row_indices[j]) = lrow - (in_row2 - in_row1 + 1);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:3049:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(newmat.row_indices[j]) = lrow;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:3052:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(newmat.values[j]) = (*it);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:3062:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(newmat.col_ptrs[i]) += newmat.col_ptrs[i - 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:3113:40:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    if(values)       { memory::release(access::rw(values));      }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:3114:40:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    if(row_indices)  { memory::release(access::rw(row_indices)); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:3116:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(values)      = new_values;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:3117:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(row_indices) = new_row_indices;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:3120:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_nonzero) -= diff;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:3142:35:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(col_ptrs)  { memory::release(access::rw(col_ptrs)); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:3143:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(col_ptrs) = new_col_ptrs;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:3146:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_cols) = new_n_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:3147:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_elem) = n_cols * n_rows;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4012:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(new_row_indices[n_nonzero]) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4029:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(new_col_ptrs[i]) += new_col_ptrs[i - 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4033:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(row_indices)  { memory::release(access::rw(row_indices)); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4034:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(col_ptrs)     { memory::release(access::rw(col_ptrs));    } 
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4036:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(row_indices) = new_row_indices;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4037:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(col_ptrs)    = new_col_ptrs;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4040:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_rows) = in_rows;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4041:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_cols) = in_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4069:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(row_indices[i]) = t_index;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4072:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(row_indices[n_nonzero]) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4074:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(col_ptrs[0]) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4075:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(col_ptrs[1]) = n_nonzero;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4076:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(col_ptrs[2]) = std::numeric_limits<uword>::max();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4078:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_rows) = (n_rows * n_cols);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4079:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_cols) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4135:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  eT* rw_values = access::rwp(values);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4195:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  eT* rw_values = access::rwp(values);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4231:23:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    arrayops::replace(access::rwp(values), n_nonzero, old_val, new_val);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4253:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::clean(access::rwp(values), n_nonzero, threshold);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4356:25:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::inplace_set(access::rwp(values), eT(1), N);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4358:35:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  for(uword i = 0; i <  N; ++i) { access::rw(row_indices[i]) = i; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4360:35:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  for(uword i = 0; i <= N; ++i) { access::rw(col_ptrs[i])    = i; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4363:46:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  for(uword i = (N+1); i <= in_cols; ++i)  { access::rw(col_ptrs[i]) = N; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4365:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_nonzero) = N;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4435:30:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arma_rng::randu<eT>::fill( access::rwp(values), new_n_nonzero );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4469:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(row_indices[cur_index]) = lrow;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4470:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(col_ptrs[lcol + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4486:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(col_ptrs[lcol]) += col_ptrs[lcol - 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4521:30:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arma_rng::randn<eT>::fill( access::rwp(values), new_n_nonzero );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4555:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(row_indices[cur_index]) = lrow;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4556:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(col_ptrs[lcol + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:4572:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(col_ptrs[lcol]) += col_ptrs[lcol - 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5084:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(values     )  { memory::release(access::rw(values));      }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5085:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(row_indices)  { memory::release(access::rw(row_indices)); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5086:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(col_ptrs   )  { memory::release(access::rw(col_ptrs));    }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5133:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(col_ptrs)    = memory::acquire<uword>(in_cols + 2);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5134:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(values)      = memory::acquire<eT>   (new_n_nonzero + 1);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5135:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(row_indices) = memory::acquire<uword>(new_n_nonzero + 1);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5140:24:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::fill_zeros(access::rwp(col_ptrs), in_cols + 1);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5142:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(col_ptrs[in_cols + 1]) = std::numeric_limits<uword>::max();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5144:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(     values[new_n_nonzero]) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5145:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(row_indices[new_n_nonzero]) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5148:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_rows)    = in_rows;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5149:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_cols)    = in_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5150:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_elem)    = (in_rows * in_cols);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5151:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_nonzero) = new_n_nonzero;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5169:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(tmp.n_rows) = tmp.n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5170:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(tmp.n_cols) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5178:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(tmp.n_rows) = 1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5179:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(tmp.n_cols) = tmp.n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5285:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(values[i])      = x_val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5286:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(row_indices[i]) = x_row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5288:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(col_ptrs[ x_col + 1 ])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5296:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(col_ptrs[i + 1]) += col_ptrs[i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5340:39:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(x.values     )  { arrayops::copy(access::rwp(values),      x.values,      x.n_nonzero + 1); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5341:39:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(x.row_indices)  { arrayops::copy(access::rwp(row_indices), x.row_indices, x.n_nonzero + 1); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5342:39:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(x.col_ptrs   )  { arrayops::copy(access::rwp(col_ptrs),    x.col_ptrs,    x.n_cols    + 1); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5358:24:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::fill_zeros(access::rwp(col_ptrs), n_cols + 1);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5431:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(values[i])      = vals[index];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5432:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(row_indices[i]) = row_i;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5434:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(col_ptrs[ col_i + 1 ])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5471:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(values[i])      = vals[i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5472:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(row_indices[i]) = row_i;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5474:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(col_ptrs[ col_i + 1 ])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5481:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(col_ptrs[i + 1]) += col_ptrs[i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5501:24:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::fill_zeros(access::rwp(col_ptrs), n_cols + 1);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5559:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(values[count])      = vals[ sorted_indices[i] ];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5560:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(row_indices[count]) = locs_i[0];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5562:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(col_ptrs[ locs_i[1] + 1 ])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5574:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          access::rw(values[count]) += vals[ sorted_indices[i] ];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5579:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          access::rw(values[count])      = vals[ sorted_indices[i] ];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5580:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          access::rw(row_indices[count]) = locs_i[0];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5582:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          access::rw(col_ptrs[ locs_i[1] + 1 ])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5616:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(values[count])      = vals[i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5617:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(row_indices[count]) = locs_i[0];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5619:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(col_ptrs[ locs_i[1] + 1 ])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5637:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(values[count]) += vals[i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5643:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(values[count])      = vals[i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5644:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(row_indices[count]) = locs_i[0];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5646:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(col_ptrs[ locs_i[1] + 1 ])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5654:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(col_ptrs[i + 1]) += col_ptrs[i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5726:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(values)       { memory::release(access::rw(values));      }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5727:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(row_indices)  { memory::release(access::rw(row_indices)); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5729:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(values)      = new_values;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5730:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(row_indices) = new_row_indices;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5734:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(     values[new_n_nonzero]) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5735:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(row_indices[new_n_nonzero]) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5737:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_nonzero) = new_n_nonzero;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5792:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(tmp.values[new_index])      = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5793:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(tmp.row_indices[new_index]) = it.row();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5794:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(tmp.col_ptrs[it.col() + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5801:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(tmp.col_ptrs[i + 1]) += tmp.col_ptrs[i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5859:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(values     )  { memory::release(access::rw(values));      }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5860:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(row_indices)  { memory::release(access::rw(row_indices)); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5861:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(col_ptrs   )  { memory::release(access::rw(col_ptrs));    }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5863:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_rows)    = x.n_rows;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5864:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_cols)    = x.n_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5865:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_elem)    = x.n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5866:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_nonzero) = x.n_nonzero;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5868:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(values)      = x.values;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5869:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(row_indices) = x.row_indices;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5870:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(col_ptrs)    = x.col_ptrs;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5873:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(x.n_rows)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5874:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(x.n_cols)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5875:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(x.n_elem)    = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5876:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(x.n_nonzero) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5878:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(x.values)      = NULL;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5879:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(x.row_indices) = NULL;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5880:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(x.col_ptrs)    = NULL;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5901:20:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    eT* t_values = access::rwp(values);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5947:22:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      arrayops::copy(access::rwp(row_indices), x.row_indices, x.n_nonzero + 1);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5948:22:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      arrayops::copy(access::rwp(col_ptrs),    x.col_ptrs,    x.n_cols    + 1);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5957:27:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          eT*  t_values = access::rwp(values);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5987:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(row_indices[it.pos()]) = it.row();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5988:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(values[it.pos()]) = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5989:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      ++access::rw(col_ptrs[it.col() + 1]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:5996:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(col_ptrs[c]) += col_ptrs[c - 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6487:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(*val_ptr) = in_val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6513:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(*val_ptr) = new_val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6539:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(*val_ptr) = new_val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6565:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(*val_ptr) = new_val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6591:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(*val_ptr) = new_val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6642:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(values[pos]) = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6644:14:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      return access::rw(values[pos]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6656:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(col_ptrs[i])++; // We are only inserting one new element.
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6661:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_nonzero)++; // Add to count of nonzero elements.
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6683:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(values)       { memory::release(access::rw(values));      }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6684:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(row_indices)  { memory::release(access::rw(row_indices)); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6686:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(values)      = new_values;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6687:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(row_indices) = new_row_indices;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6689:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw(values[pos]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6723:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        --access::rw(n_nonzero); // Remove one from the count of nonzero elements.
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6740:44:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        if(values)       { memory::release(access::rw(values));      }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6741:44:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        if(row_indices)  { memory::release(access::rw(row_indices)); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6743:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(values)      = new_values;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6744:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(row_indices) = new_row_indices;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpMat_meat.hpp:6749:13:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          --access::rw(col_ptrs[i]); // We only removed one element.
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpRow_meat.hpp:294:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(SpMat<eT>::values) = new_values;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpRow_meat.hpp:295:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(SpMat<eT>::row_indices) = new_row_indices;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpRow_meat.hpp:297:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(SpMat<eT>::n_nonzero) -= elem_diff;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpRow_meat.hpp:319:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(SpMat<eT>::col_ptrs) = new_col_ptrs;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpRow_meat.hpp:321:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(SpMat<eT>::n_cols) -= diff;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpRow_meat.hpp:322:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(SpMat<eT>::n_elem) -= diff;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_iterators_meat.hpp:525:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(*iterator_base::M),
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_iterators_meat.hpp:526:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    &(access::rw(iterator_base::M->m.values[iterator_base::internal_pos + const_iterator::skip_pos])));
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_iterators_meat.hpp:1127:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(*iterator_base::M),
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_iterators_meat.hpp:1128:6:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    &access::rw(iterator_base::M->m.values[const_row_iterator::actual_pos]));
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:50:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_nonzero) = count;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:84:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_nonzero) = count;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:161:32:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        eT*    m_values      = access::rwp(m.values);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:189:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(m).remove_zeros();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:193:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(n_nonzero) = n_nonzero - (old_m_n_nonzero - m.n_nonzero); 
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:221:32:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        eT*    m_values      = access::rwp(m.values);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:249:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(m).remove_zeros();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:253:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(n_nonzero) = n_nonzero - (old_m_n_nonzero - m.n_nonzero); 
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:530:32:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        eT*    m_values      = access::rwp(m.values);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:558:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(m).remove_zeros();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:562:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(n_nonzero) = n_nonzero - (old_m_n_nonzero - m.n_nonzero); 
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:625:32:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        eT*    m_values      = access::rwp(m.values);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:653:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(m).remove_zeros();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:657:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(n_nonzero) = n_nonzero - (old_m_n_nonzero - m.n_nonzero); 
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:695:32:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        eT*    m_values      = access::rwp(m.values);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:738:27:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if(new_val == eT(0))  { access::rw(m).remove_zeros(); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:805:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(m).zeros();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:806:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_nonzero) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:832:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(tmp.values[tmp_count])      = (*m_it);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:833:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(tmp.row_indices[tmp_count]) = m_it_row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:834:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(tmp.col_ptrs[m_it_col + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:841:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(tmp.col_ptrs[i + 1]) += tmp.col_ptrs[i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:844:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(m).steal_mem(tmp);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:846:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_nonzero) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:1207:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw(m).submat(in_row1 + aux_row1, in_col1 + aux_col1, in_row2 + aux_row1, in_col2 + aux_col1);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:1374:20:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    const eT val = access::rw(m).at(in_row1 + aux_row1, c);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:1375:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(m).at(in_row2 + aux_row1, c) = eT( access::rw(m).at(in_row1 + aux_row1, c) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:1375:51:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(m).at(in_row2 + aux_row1, c) = eT( access::rw(m).at(in_row1 + aux_row1, c) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:1376:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(m).at(in_row1 + aux_row1, c) = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:1396:20:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    const eT val = access::rw(m).at(r, in_col1 + aux_col1);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:1397:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(m).at(r, in_col1 + aux_col1) = eT( access::rw(m).at(r, in_col2 + aux_col1) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:1397:51:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(m).at(r, in_col1 + aux_col1) = eT( access::rw(m).at(r, in_col2 + aux_col1) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:1398:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(m).at(r, in_col2 + aux_col1) = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:1589:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  eT& retval = access::rw(m).insert_element(in_row + aux_row1, in_col + aux_col1, in_val);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:1591:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_nonzero) += (m.n_nonzero - old_n_nonzero);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:1607:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(m).delete_element(in_row + aux_row1, in_col + aux_col1);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpSubview_meat.hpp:1608:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_nonzero) -= (old_n_nonzero - m.n_nonzero);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpValProxy_meat.hpp:349:13:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return T( access::tmp_real( (val_ptr) ? eT(*val_ptr) : eT(0) ) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/SpValProxy_meat.hpp:361:13:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return T( access::tmp_imag( (val_ptr) ? eT(*val_ptr) : eT(0) ) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/access.hpp:21:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
class access
data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_str.hpp:26:32:  [4] (format) snprintf:
  If format strings can be influenced by an attacker, they can be exploited,
  and note that sprintf variations do not always \0-terminate (CWE-134). Use
  a constant for the format specification.
    #define arma_snprintf std::snprintf
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:71:56:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      blas_int lwork_proposed = static_cast<blas_int>( access::tmp_real(work_query[0]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:609:39:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    sword sign = (is_cx<eT>::no) ? ( (access::tmp_real( tmp.at(0,0) ) < T(0)) ? -1 : +1 ) : +1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:610:47:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    eT    val  = (is_cx<eT>::no) ? std::log( (access::tmp_real( tmp.at(0,0) ) < T(0)) ? tmp.at(0,0)*T(-1) : tmp.at(0,0) ) : std::log( tmp.at(0,0) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:616:36:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      sign *= (is_cx<eT>::no) ? ( (access::tmp_real(x) < T(0)) ? -1 : +1 ) : +1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:617:44:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      val  += (is_cx<eT>::no) ? std::log( (access::tmp_real(x) < T(0)) ? x*T(-1) : x ) : std::log(x);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:660:39:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    sword sign = (is_cx<eT>::no) ? ( (access::tmp_real( tmp.at(0,0) ) < T(0)) ? -1 : +1 ) : +1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:661:47:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    eT    val  = (is_cx<eT>::no) ? std::log( (access::tmp_real( tmp.at(0,0) ) < T(0)) ? tmp.at(0,0)*T(-1) : tmp.at(0,0) ) : std::log( tmp.at(0,0) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:667:36:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      sign *= (is_cx<eT>::no) ? ( (access::tmp_real(x) < T(0)) ? -1 : +1 ) : +1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:668:44:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      val  += (is_cx<eT>::no) ? std::log( (access::tmp_real(x) < T(0)) ? x*T(-1) : x ) : std::log(x);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:2529:48:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
       lwork_proposed = static_cast<blas_int>( access::tmp_real(work_query[0]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:2832:54:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    blas_int lwork_proposed = static_cast<blas_int>( access::tmp_real(work_query[0]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:2940:54:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    blas_int lwork_proposed = static_cast<blas_int>( access::tmp_real(work_query[0]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:3036:54:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    blas_int lwork_proposed = static_cast<blas_int>( access::tmp_real(work_query[0]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:3130:54:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    blas_int lwork_proposed = static_cast<blas_int>( access::tmp_real(work_query[0]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:3307:47:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      lwork_proposed = static_cast<blas_int>( access::tmp_real(work_query[0]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:3495:47:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      lwork_proposed = static_cast<blas_int>( access::tmp_real(work_query[0]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:3731:47:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      lwork_proposed = static_cast<blas_int>( access::tmp_real(work_query[0]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:3897:47:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      lwork_proposed = static_cast<blas_int>( access::tmp_real(work_query[0]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:4089:47:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      lwork_proposed = static_cast<blas_int>( access::tmp_real(work_query[0]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:4261:47:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      lwork_proposed = static_cast<blas_int>( access::tmp_real(work_query[0]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:5172:47:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      lwork_proposed = static_cast<blas_int>( access::tmp_real(work_query[0]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:5270:47:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      lwork_proposed = static_cast<blas_int>( access::tmp_real(work_query[0]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:5442:54:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    blas_int lwork_proposed = static_cast<blas_int>( access::tmp_real(work_query[0]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/auxlib_meat.hpp:5564:54:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    blas_int lwork_proposed = static_cast<blas_int>( access::tmp_real( work_query[0]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:2998:37:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    f.read( reinterpret_cast<char*>(access::rwp(x.values)),      std::streamsize(x.n_nonzero*sizeof(eT))     );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:3002:37:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    f.read( reinterpret_cast<char*>(access::rwp(x.row_indices)), std::streamsize(x.n_nonzero*sizeof(uword))  );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:3003:37:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    f.read( reinterpret_cast<char*>(access::rwp(x.col_ptrs)),    std::streamsize((x.n_cols+1)*sizeof(uword)) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:3036:29:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          arrayops::convert(access::rwp(x.row_indices), tmp_a.memptr(), x.n_nonzero );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:3037:29:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          arrayops::convert(access::rwp(x.col_ptrs),    tmp_b.memptr(), x.n_cols + 1);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:4504:22:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      tmp[i+0] = u8( access::tmp_real( x.at(row,col,0) ) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:4505:22:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      tmp[i+1] = u8( access::tmp_real( x.at(row,col,1) ) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:4506:22:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      tmp[i+2] = u8( access::tmp_real( x.at(row,col,2) ) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:4727:20:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    tmp[i+0] = u8( access::tmp_real( R.at(row,col) ) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:4728:20:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    tmp[i+1] = u8( access::tmp_real( G.at(row,col) ) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:4729:20:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    tmp[i+2] = u8( access::tmp_real( B.at(row,col) ) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:390:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(X.n_rows  ) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:391:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(X.n_cols  ) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:392:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(X.n_slices) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:393:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(X.n_elem  ) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:394:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(X.mem     ) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:408:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_rows  ) = X.n_rows;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:409:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_cols  ) = X.n_cols;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:410:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_slices) = X.n_slices;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:411:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_elem  ) = X.n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:423:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(X.n_rows  ) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:424:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(X.n_cols  ) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:425:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(X.n_elem  ) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:426:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(X.n_slices) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:427:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(X.mem     ) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:1968:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_rows)   = n_rows_in;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:1969:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_cols)   = n_cols_in;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:1970:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_slices) = n_slices_in;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:1998:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_rows)   = n_rows_in;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:1999:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_cols)   = n_cols_in;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:2000:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_slices) = n_slices_in;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/field_meat.hpp:2001:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(n_elem)   = n_elem_new;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_clamp.hpp:81:20:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  eT* out_values = access::rwp(out.values);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_conv_to.hpp:539:22:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::convert( access::rwp(out.values), X.values, X.n_nonzero );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_conv_to.hpp:563:25:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::convert_cx( access::rwp(out.values), X.values, X.n_nonzero );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_log_det.hpp:86:34:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  T  sign = (is_cx<eT>::no) ? ( (access::tmp_real(x) < T(0)) ? -1 : +1 ) : +1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_log_det.hpp:87:42:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  eT val  = (is_cx<eT>::no) ? std::log( (access::tmp_real(x) < T(0)) ? x*T(-1) : x ) : std::log(x);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_log_det.hpp:93:34:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    sign *= (is_cx<eT>::no) ? ( (access::tmp_real(x) < T(0)) ? -1 : +1 ) : +1;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_log_det.hpp:94:42:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    val  += (is_cx<eT>::no) ? std::log( (access::tmp_real(x) < T(0)) ? x*T(-1) : x ) : std::log(x);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_norm.hpp:194:26:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    Col<eT> fake_vector( access::rwp(A.values), A.n_nonzero, false );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_norm.hpp:265:24:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  Col<eT> fake_vector( access::rwp(A.values), A.n_nonzero, false );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_spones.hpp:38:26:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::inplace_set( access::rwp(out.values), eT(1), out.n_nonzero );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_sprandn.hpp:118:30:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arma_rng::randn<eT>::fill( access::rwp(out.values), out.n_nonzero );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/fn_sprandu.hpp:118:30:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arma_rng::randu<eT>::fill( access::rwp(out.values), out.n_nonzero );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:163:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(means) = in_means;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:164:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(dcovs) = in_dcovs;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:165:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(hefts) = in_hefts;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:187:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(means) = in_means;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:208:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(dcovs) = in_dcovs;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:238:28:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        eT*    hefts_mem = access::rw(hefts).memptr();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:245:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(hefts) /= accu(hefts);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:296:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(hefts) = Q.slice(0).row(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:297:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(means) = Q.slice(0).submat(1, 0, Q.n_rows-1, Q.n_cols-1);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:298:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(dcovs) = Q.slice(1).submat(1, 0, Q.n_rows-1, Q.n_cols-1);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:829:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(means) = user_means;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:840:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(means).zeros(X.n_rows, N_gaus);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:885:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(t.means) = x.means;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:886:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(t.dcovs) = x.dcovs;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:887:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(t.hefts) = x.hefts;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:902:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(hefts) = x.hefts;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:903:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(means) = x.means;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:908:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(dcovs).zeros(N_dims,N_gaus);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:914:20:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    eT* dcov_mem = access::rw(dcovs).colptr(g);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:934:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(means).zeros(in_n_dims, in_n_gaus);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:936:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(dcovs).ones(in_n_dims, in_n_gaus);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:938:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(hefts).set_size(in_n_gaus);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:940:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(hefts).fill(eT(1) / eT(in_n_gaus));
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:993:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  eT* hefts_mem = access::rw(hefts).memptr();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:1820:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(means) = X.cols(initial_indices);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:1836:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(means).col(0) = X.unsafe_col(start_index);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:1884:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(means).col(g) = X.unsafe_col(best_i);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:2019:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  eT* hefts_mem = access::rw(hefts).memptr();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:2027:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    eT* mean = access::rw(means).colptr(g);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:2028:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    eT* dcov = access::rw(dcovs).colptr(g);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:2196:22:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      eT* new_mean = access::rw(new_means).colptr(g);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:2274:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(means) = old_means;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:2441:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  eT* hefts_mem = access::rw(hefts).memptr();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:2495:22:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      eT* mean_mem = access::rw(means).colptr(g);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:2496:22:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      eT* dcov_mem = access::rw(dcovs).colptr(g);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:2598:30:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        eT*   dcovs_mem    = access::rw(dcovs).memptr();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:2610:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  eT* hefts_mem = access::rw(hefts).memptr();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_diag_meat.hpp:2644:89:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if((heft_sum < (eT(1) - Datum<eT>::eps)) || (heft_sum > (eT(1) + Datum<eT>::eps)))  { access::rw(hefts) /= heft_sum; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:167:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(means) = in_means;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:168:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(fcovs) = in_fcovs;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:169:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(hefts) = in_hefts;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:191:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(means) = in_means;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:216:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(fcovs) = in_fcovs;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:246:28:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        eT*    hefts_mem = access::rw(hefts).memptr();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:253:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(hefts) /= accu(hefts);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:315:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(means) = storage_means;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:316:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(hefts) = storage_hefts;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:329:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(fcovs).slice(g) = storage_fcov;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:847:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(t.means) = x.means;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:848:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(t.fcovs) = x.fcovs;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:849:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(t.hefts) = x.hefts;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:864:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(hefts) = x.hefts;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:865:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(means) = x.means;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:870:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(fcovs).zeros(N_dims,N_dims,N_gaus);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:874:21:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    Mat<eT>& fcov = access::rw(fcovs).slice(g);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:896:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(means).zeros(in_n_dims, in_n_gaus);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:898:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(fcovs).zeros(in_n_dims, in_n_dims, in_n_gaus);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:902:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(fcovs).slice(g).diag().ones();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:905:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(hefts).set_size(in_n_gaus);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:906:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(hefts).fill(eT(1) / eT(in_n_gaus));
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:974:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  eT* hefts_mem = access::rw(hefts).memptr();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:1847:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(means) = X.cols(initial_indices);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:1863:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(means).col(0) = X.unsafe_col(start_index);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:1911:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(means).col(g) = X.unsafe_col(best_i);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:2046:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  eT* hefts_mem = access::rw(hefts).memptr();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:2054:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    eT* mean = access::rw(means).colptr(g);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:2056:21:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    Mat<eT>& fcov = access::rw(fcovs).slice(g);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:2225:22:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      eT* new_mean = access::rw(new_means).colptr(g);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:2303:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(means) = old_means;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:2477:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  eT* hefts_mem = access::rw(hefts).memptr();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:2553:22:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      eT* mean_mem = access::rw(means).colptr(g);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:2560:23:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      Mat<eT>& fcov = access::rw(fcovs).slice(g);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:2633:27:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      Mat<eT>& acc_fcov = access::rw(acc_fcovs).slice(g);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:2678:21:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    Mat<eT>& fcov = access::rw(fcovs).slice(g);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:2691:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  eT* hefts_mem = access::rw(hefts).memptr();
data/armadillo-9.900.1+dfsg/include/armadillo_bits/gmm_full_meat.hpp:2725:89:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  if((heft_sum < (eT(1) - Datum<eT>::eps)) || (heft_sum > (eT(1) + Datum<eT>::eps)))  { access::rw(hefts) /= heft_sum; }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/injector_meat.hpp:55:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.mem),    access::rw(B.mem)    );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/injector_meat.hpp:55:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.mem),    access::rw(B.mem)    );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/injector_meat.hpp:56:16:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_elem), access::rw(B.n_elem) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/injector_meat.hpp:56:38:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    std::swap( access::rw(A.n_elem), access::rw(B.n_elem) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_index_max_meat.hpp:116:71:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        T  col_val = (is_cx<eT>::yes) ? T(std::abs(col_mem[row])) : T(access::tmp_real(col_mem[row]));
data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_index_min_meat.hpp:116:71:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        T  col_val = (is_cx<eT>::yes) ? T(std::abs(col_mem[row])) : T(access::tmp_real(col_mem[row]));
data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_orth_null_meat.hpp:32:17:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  const T tol = access::tmp_real(expr.aux);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_orth_null_meat.hpp:108:17:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  const T tol = access::tmp_real(expr.aux);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/op_pinv_meat.hpp:32:17:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  const T tol = access::tmp_real(in.aux);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/operator_div.hpp:226:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(result.values[cur_pos]) = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/operator_div.hpp:227:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(result.row_indices[cur_pos]) = row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/operator_div.hpp:228:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      ++access::rw(result.col_ptrs[col + 1]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/operator_div.hpp:236:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(result.col_ptrs[col]) += result.col_ptrs[col - 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/podarray_meat.hpp:186:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw(mem[i]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/podarray_meat.hpp:210:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw(mem[i]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/podarray_meat.hpp:412:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(n_elem) = new_n_elem;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/running_stat_vec_meat.hpp:66:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(calc_cov) = in_rsv.calc_cov;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spdiagview_meat.hpp:212:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(tmp1.values[i]) = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spdiagview_meat.hpp:709:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.row_indices[count]) = i;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spdiagview_meat.hpp:710:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.values[count])      = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spdiagview_meat.hpp:715:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(out.col_ptrs[0]) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spdiagview_meat.hpp:716:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(out.col_ptrs[1]) = d_n_nonzero;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spdiagview_meat.hpp:881:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          access::rw(tmp.values[count])      = (*it);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spdiagview_meat.hpp:882:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          access::rw(tmp.row_indices[count]) = row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spdiagview_meat.hpp:883:11:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
          access::rw(tmp.col_ptrs[col + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spdiagview_meat.hpp:890:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(tmp.col_ptrs[i + 1]) += tmp.col_ptrs[i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spdiagview_meat.hpp:894:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(         tmp.n_nonzero) = count;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spdiagview_meat.hpp:895:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(     tmp.values[count]) = eT(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spdiagview_meat.hpp:896:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(tmp.row_indices[count]) = uword(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spdiagview_meat.hpp:898:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(m).steal_mem(tmp);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spdiagview_meat.hpp:912:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(m).steal_mem(tmp2);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_join_meat.hpp:239:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::copy( access::rwp(out.values),          A.values, A_n_nz   );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_join_meat.hpp:240:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::copy( access::rwp(out.values) + A_n_nz, B.values, B_n_nz+1 );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_join_meat.hpp:242:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::copy( access::rwp(out.row_indices),          A.row_indices, A_n_nz   );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_join_meat.hpp:243:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::copy( access::rwp(out.row_indices) + A_n_nz, B.row_indices, B_n_nz+1 );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_join_meat.hpp:245:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::copy( access::rwp(out.col_ptrs),            A.col_ptrs, A_n_cols   );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_join_meat.hpp:246:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::copy( access::rwp(out.col_ptrs) + A_n_cols, B.col_ptrs, B_n_cols+2 );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_join_meat.hpp:248:27:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::inplace_plus( access::rwp(out.col_ptrs) + A_n_cols, A_n_nz, B_n_cols+1 );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_kron_meat.hpp:69:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(out.col_ptrs[0]) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_kron_meat.hpp:84:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(out.values[count])      = A_val * B.values[B_i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_kron_meat.hpp:85:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(out.row_indices[count]) = out_row + B.row_indices[B_i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_kron_meat.hpp:91:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(out.col_ptrs[A_col * B_n_cols + B_col + 1]) = count;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_max_meat.hpp:118:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.values[count]) = out_val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_max_meat.hpp:123:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.row_indices[count]) = out_row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_max_meat.hpp:124:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.col_ptrs[out_col + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_max_meat.hpp:131:21:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  uword* col_ptrs = access::rwp(out.col_ptrs);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_max_meat.hpp:148:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(         out.n_nonzero) = count;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_max_meat.hpp:149:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(     out.values[count]) = eT(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_max_meat.hpp:150:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.row_indices[count]) = uword(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:34:18:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  SpMat<eT>& A = access::rw(sv.m);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:59:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(tmp.values[tmp_count])      = (*B_it);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:60:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(tmp.row_indices[tmp_count]) = B_it.row() + sv_row_start;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:61:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(tmp.col_ptrs[B_it.col() + sv_col_start + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:67:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(tmp.col_ptrs[i + 1]) += tmp.col_ptrs[i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:72:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(sv.n_nonzero) = B.n_nonzero;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:163:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.values[count]) = out_val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:168:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.row_indices[count]) = out_row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:169:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.col_ptrs[out_col + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:181:21:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  uword* col_ptrs = access::rwp(out.col_ptrs);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:190:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(sv.n_nonzero) = B.n_nonzero;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:217:18:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  SpMat<eT>& A = access::rw(sv.m);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:246:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(tmp.values[tmp_count])      = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:247:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(tmp.row_indices[tmp_count]) = B_it.row() + sv_row_start;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:248:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(tmp.col_ptrs[B_it.col() + sv_col_start + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:255:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(tmp.col_ptrs[i + 1]) += tmp.col_ptrs[i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:260:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(sv.n_nonzero) = B_n_nonzero;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:351:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.values[count]) = out_val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:356:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.row_indices[count]) = out_row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:357:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.col_ptrs[out_col + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:369:21:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  uword* col_ptrs = access::rwp(out.col_ptrs);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:378:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(sv.n_nonzero) = B_n_nonzero;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:440:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(out.values[count]) = out_val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:445:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(out.row_indices[count]) = out_row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:446:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(out.col_ptrs[out_col + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:452:21:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  uword* col_ptrs = access::rwp(out.col_ptrs);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:461:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(         out.n_nonzero) = count;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:462:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(     out.values[count]) = eT(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:463:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(out.row_indices[count]) = uword(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:525:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(out.values[count]) = out_val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:530:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(out.row_indices[count]) = out_row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:531:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(out.col_ptrs[out_col + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:537:21:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  uword* col_ptrs = access::rwp(out.col_ptrs);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:546:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(         out.n_nonzero) = count;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:547:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(     out.values[count]) = eT(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_merge_meat.hpp:548:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(out.row_indices[count]) = uword(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_min_meat.hpp:118:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.values[count]) = out_val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_min_meat.hpp:123:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.row_indices[count]) = out_row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_min_meat.hpp:124:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.col_ptrs[out_col + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_min_meat.hpp:131:21:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  uword* col_ptrs = access::rwp(out.col_ptrs);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_min_meat.hpp:148:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(         out.n_nonzero) = count;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_min_meat.hpp:149:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(     out.values[count]) = eT(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_min_meat.hpp:150:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.row_indices[count]) = uword(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_minus_meat.hpp:119:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.values[count]) = out_val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_minus_meat.hpp:124:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.row_indices[count]) = out_row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_minus_meat.hpp:125:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.col_ptrs[out_col + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_minus_meat.hpp:132:21:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  uword* col_ptrs = access::rwp(out.col_ptrs);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_minus_meat.hpp:149:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(         out.n_nonzero) = count;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_minus_meat.hpp:150:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(     out.values[count]) = eT(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_minus_meat.hpp:151:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.row_indices[count]) = uword(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_minus_meat.hpp:204:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < A.n_nonzero; ++i)  { access::rw(AA.values[i]) = out_eT(A.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_minus_meat.hpp:225:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < B.n_nonzero; ++i)  { access::rw(BB.values[i]) = out_eT(B.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_minus_meat.hpp:242:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < A.n_nonzero; ++i)  { access::rw(AA.values[i]) = out_eT(A.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_minus_meat.hpp:243:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < B.n_nonzero; ++i)  { access::rw(BB.values[i]) = out_eT(B.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_plus_meat.hpp:119:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.values[count]) = out_val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_plus_meat.hpp:124:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.row_indices[count]) = out_row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_plus_meat.hpp:125:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.col_ptrs[out_col + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_plus_meat.hpp:132:21:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  uword* col_ptrs = access::rwp(out.col_ptrs);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_plus_meat.hpp:149:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(         out.n_nonzero) = count;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_plus_meat.hpp:150:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(     out.values[count]) = eT(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_plus_meat.hpp:151:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.row_indices[count]) = uword(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_plus_meat.hpp:204:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < A.n_nonzero; ++i)  { access::rw(AA.values[i]) = out_eT(A.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_plus_meat.hpp:225:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < B.n_nonzero; ++i)  { access::rw(BB.values[i]) = out_eT(B.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_plus_meat.hpp:242:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < A.n_nonzero; ++i)  { access::rw(AA.values[i]) = out_eT(A.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_plus_meat.hpp:243:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < B.n_nonzero; ++i)  { access::rw(BB.values[i]) = out_eT(B.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_relational_meat.hpp:114:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.values[count]) = out_val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_relational_meat.hpp:119:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.row_indices[count]) = out_row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_relational_meat.hpp:120:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.col_ptrs[out_col + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_relational_meat.hpp:127:21:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  uword* col_ptrs = access::rwp(out.col_ptrs);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_relational_meat.hpp:144:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(         out.n_nonzero) = count;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_relational_meat.hpp:145:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(     out.values[count]) = eT(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_relational_meat.hpp:146:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.row_indices[count]) = uword(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_relational_meat.hpp:245:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.values[count]) = out_val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_relational_meat.hpp:250:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.row_indices[count]) = out_row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_relational_meat.hpp:251:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.col_ptrs[out_col + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_relational_meat.hpp:258:21:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  uword* col_ptrs = access::rwp(out.col_ptrs);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_relational_meat.hpp:275:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(         out.n_nonzero) = count;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_relational_meat.hpp:276:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(     out.values[count]) = eT(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_relational_meat.hpp:277:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.row_indices[count]) = uword(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:97:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(out.values[count]) = out_val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:99:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(out.row_indices[count]) = x_it_row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:100:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(out.col_ptrs[x_it_col + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:122:21:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  uword* col_ptrs = access::rwp(out.col_ptrs);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:139:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(         out.n_nonzero) = count;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:140:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(     out.values[count]) = eT(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:141:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.row_indices[count]) = uword(0);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:213:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(        out.values[count]) = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:214:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(   out.row_indices[count]) = it2_row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:215:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.col_ptrs[it2_col + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:225:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(out.col_ptrs[c]) += out.col_ptrs[c - 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:261:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < A.n_nonzero; ++i)  { access::rw(AA.values[i]) = out_eT(A.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:282:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < B.n_nonzero; ++i)  { access::rw(BB.values[i]) = out_eT(B.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:299:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < A.n_nonzero; ++i)  { access::rw(AA.values[i]) = out_eT(A.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:300:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < B.n_nonzero; ++i)  { access::rw(BB.values[i]) = out_eT(B.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:356:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(        out.values[count]) = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:357:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(   out.row_indices[count]) = it2_row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:358:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.col_ptrs[it2_col + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_schur_meat.hpp:368:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(out.col_ptrs[c]) += out.col_ptrs[c - 1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_times_meat.hpp:157:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(c.col_ptrs[old_col + 1]) = cur_col_length;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_times_meat.hpp:174:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(c.col_ptrs[i + 1]) += c.col_ptrs[i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_times_meat.hpp:198:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(c.col_ptrs[cur_col]) = cur_pos;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_times_meat.hpp:208:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(c.col_ptrs[cur_col]) = cur_pos;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_times_meat.hpp:271:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(c.row_indices[cur_pos]) = row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_times_meat.hpp:272:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(c.values[cur_pos]) = sums[row];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_times_meat.hpp:283:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(c.col_ptrs[c.n_cols]) = cur_pos;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_times_meat.hpp:507:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < A.n_nonzero; ++i)  { access::rw(AA.values[i]) = out_eT(A.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_times_meat.hpp:528:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < B.n_nonzero; ++i)  { access::rw(BB.values[i]) = out_eT(B.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_times_meat.hpp:545:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < A.n_nonzero; ++i)  { access::rw(AA.values[i]) = out_eT(A.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_times_meat.hpp:546:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < B.n_nonzero; ++i)  { access::rw(BB.values[i]) = out_eT(B.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_times_meat.hpp:580:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < A.n_nonzero; ++i)  { access::rw(AA.values[i]) = out_eT(A.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_times_meat.hpp:615:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < A.n_nonzero; ++i)  { access::rw(AA.values[i]) = out_eT(A.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_times_meat.hpp:670:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < B.n_nonzero; ++i)  { access::rw(BB.values[i]) = out_eT(B.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spglue_times_meat.hpp:688:45:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    for(uword i=0; i < B.n_nonzero; ++i)  { access::rw(BB.values[i]) = out_eT(B.values[i]); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_htrans_meat.hpp:51:15:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    eT& val = access::rw(out.values[i]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_misc_meat.hpp:558:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.row_indices[count]) = i;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_misc_meat.hpp:559:7:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      access::rw(out.values[count])      = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_misc_meat.hpp:564:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(out.col_ptrs[0]) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_misc_meat.hpp:565:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(out.col_ptrs[1]) = n_nonzero;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_repmat_meat.hpp:65:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw(out.col_ptrs[0]) = 0;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_repmat_meat.hpp:78:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(out.values[count])      = B.values[B_i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_repmat_meat.hpp:79:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(out.row_indices[count]) = out_row + B.row_indices[B_i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_repmat_meat.hpp:85:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(out.col_ptrs[A_col * B_n_cols + B_col + 1]) = count;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_strans_meat.hpp:41:17:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        eT* b = access::rwp(B.values);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_strans_meat.hpp:46:21:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        uword* ib = access::rwp(B.col_ptrs);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_strans_meat.hpp:47:21:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        uword* jb = access::rwp(B.row_indices);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_trimat_meat.hpp:75:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(out.values[new_index])      = (*it);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_trimat_meat.hpp:76:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(out.row_indices[new_index]) = row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_trimat_meat.hpp:77:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(out.col_ptrs[col + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_trimat_meat.hpp:95:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(out.values[new_index])      = (*it);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_trimat_meat.hpp:96:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(out.row_indices[new_index]) = row;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_trimat_meat.hpp:97:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access::rw(out.col_ptrs[col + 1])++;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/spop_trimat_meat.hpp:107:5:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    access::rw(out.col_ptrs[i + 1]) += out.col_ptrs[i];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_each_meat.hpp:99:17:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  Cube<eT>& p = access::rw(subview_cube_each_common<eT>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_each_meat.hpp:124:17:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  Cube<eT>& p = access::rw(subview_cube_each_common<eT>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_each_meat.hpp:149:17:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  Cube<eT>& p = access::rw(subview_cube_each_common<eT>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_each_meat.hpp:174:17:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  Cube<eT>& p = access::rw(subview_cube_each_common<eT>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_each_meat.hpp:199:17:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  Cube<eT>& p = access::rw(subview_cube_each_common<eT>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_each_meat.hpp:224:17:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  Cube<eT>& C = access::rw(subview_cube_each_common<eT>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_each_meat.hpp:275:17:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  Cube<eT>& p = access::rw(subview_cube_each_common<eT>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_each_meat.hpp:314:17:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  Cube<eT>& p = access::rw(subview_cube_each_common<eT>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_each_meat.hpp:353:17:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  Cube<eT>& p = access::rw(subview_cube_each_common<eT>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_each_meat.hpp:392:17:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  Cube<eT>& p = access::rw(subview_cube_each_common<eT>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_each_meat.hpp:431:17:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  Cube<eT>& p = access::rw(subview_cube_each_common<eT>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_meat.hpp:1461:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( (const_cast< Cube<eT>& >(m)).mem[index] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_meat.hpp:1501:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( (const_cast< Cube<eT>& >(m)).mem[index] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_meat.hpp:1536:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( (const_cast< Cube<eT>& >(m)).mem[index] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_meat.hpp:1562:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( (const_cast< Cube<eT>& >(m)).mem[index] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_cube_meat.hpp:1584:12:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return & access::rw((const_cast< Cube<eT>& >(m)).mem[  (in_slice + aux_slice1)*m.n_elem_slice + (in_col + aux_col1)*m.n_rows + aux_row1  ]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_each_meat.hpp:146:15:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  parent& p = access::rw(subview_each_common<parent,mode>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_each_meat.hpp:183:15:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  parent& p = access::rw(subview_each_common<parent,mode>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_each_meat.hpp:220:15:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  parent& p = access::rw(subview_each_common<parent,mode>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_each_meat.hpp:257:15:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  parent& p = access::rw(subview_each_common<parent,mode>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_each_meat.hpp:294:15:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  parent& p = access::rw(subview_each_common<parent,mode>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_each_meat.hpp:374:15:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  parent& p = access::rw(subview_each_common<parent,mode>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_each_meat.hpp:429:15:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  parent& p = access::rw(subview_each_common<parent,mode>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_each_meat.hpp:482:15:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  parent& p = access::rw(subview_each_common<parent,mode>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_each_meat.hpp:535:15:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  parent& p = access::rw(subview_each_common<parent,mode>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_each_meat.hpp:588:15:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  parent& p = access::rw(subview_each_common<parent,mode>::P);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:1112:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( (const_cast< Mat<eT>& >(m)).mem[index] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:1144:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( (const_cast< Mat<eT>& >(m)).mem[index] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:1175:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( (const_cast< Mat<eT>& >(m)).mem[index] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:1201:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( (const_cast< Mat<eT>& >(m)).mem[index] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:1225:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( (const_cast< Mat<eT>& >(m)).mem[index] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:1252:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( (const_cast< Mat<eT>& >(m)).mem[index] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:1277:12:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return & access::rw((const_cast< Mat<eT>& >(m)).mem[ (in_col + aux_col1)*m.n_rows + aux_row1 ]);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:2423:18:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      std::swap( access::rw(mem[pos1]), access::rw(mem[pos2]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:2423:41:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
      std::swap( access::rw(mem[pos1]), access::rw(mem[pos2]) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:3176:3:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  access::rw( colmem[0] ) = val;
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:3256:26:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::inplace_set( access::rwp(colmem), val, subview<eT>::n_rows );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:3268:25:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::fill_zeros( access::rwp(colmem), subview<eT>::n_rows );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:3280:26:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  arrayops::inplace_set( access::rwp(colmem), eT(1), subview<eT>::n_rows );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:3303:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( colmem[ii] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:3325:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( colmem[ii] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:3349:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( colmem[in_row] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:3371:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( colmem[in_row] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:3855:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( (const_cast< Mat<eT>& >(subview<eT>::m)).mem[index] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:3881:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( (const_cast< Mat<eT>& >(subview<eT>::m)).mem[index] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:3909:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( (const_cast< Mat<eT>& >(subview<eT>::m)).mem[index] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:3935:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::rw( (const_cast< Mat<eT>& >(subview<eT>::m)).mem[index] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:4369:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    out_mem[ii] = access::alt_conj( X.at(row, start_col+ii) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:4380:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::alt_conj( sv_row[ii] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:4390:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::alt_conj( sv_row[ii] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:4400:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::alt_conj( sv_row(ii) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:4410:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::alt_conj( sv_row(in_col, in_row) );  // deliberately swapped
data/armadillo-9.900.1+dfsg/include/armadillo_bits/subview_meat.hpp:4420:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::alt_conj( sv_row.at(0, in_row) );  // deliberately swapped
data/armadillo-9.900.1+dfsg/include/armadillo_bits/xtrans_mat_meat.hpp:79:30:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return really_do_conj ? eT(access::alt_conj(X.at(in_col, in_row))) : eT(X.at(in_col, in_row));
data/armadillo-9.900.1+dfsg/include/armadillo_bits/xvec_htrans_meat.hpp:50:19:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    out_mem[ii] = access::alt_conj( in_mem[ii] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/xvec_htrans_meat.hpp:61:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::alt_conj( mem[ii] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/xvec_htrans_meat.hpp:71:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::alt_conj( mem[ii] );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/xvec_htrans_meat.hpp:83:10:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
  return access::alt_conj( mem[in_row + in_col] );  // either in_row or in_col must be zero, as we're storing a vector
data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_rng_cxx98.hpp:49:8:  [3] (random) srand:
  This function is not sufficiently random for security-related functions
  such as key and nonce creation (CWE-327). Use a more secure technique for
  acquiring random values.
  std::srand(val);
data/armadillo-9.900.1+dfsg/tests/catch.hpp:8705:18:  [3] (random) srand:
  This function is not sufficiently random for security-related functions
  such as key and nonce creation (CWE-327). Use a more secure technique for
  acquiring random values.
            std::srand( config.rngSeed() );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_rng.hpp:123:18:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
        unsigned char b[sizeof(seed_type)];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_rng.hpp:162:16:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
      unsigned char b[sizeof(uword*)];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_static_check.hpp:30:18:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    static const char
data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_static_check.hpp:58:63:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
  #define arma_static_check(condition, message)  static const char message[ (condition) ? -1 : +1 ]
data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_str.hpp:123:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char  local_buffer[1024];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_str.hpp:177:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char  local_buffer[1024];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_str.hpp:231:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char  local_buffer[1024];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_str.hpp:285:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char  local_buffer[1024];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_str.hpp:339:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char  local_buffer[1024];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_str.hpp:393:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char  local_buffer[1024];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/arrayops_meat.hpp:36:12:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
      std::memcpy(dest, src, n_elem*sizeof(eT));
data/armadillo-9.900.1+dfsg/include/armadillo_bits/arrayops_meat.hpp:41:28:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
    if(n_elem > 0)  { std::memcpy(dest, src, n_elem*sizeof(eT)); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/debug.hpp:1304:20:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
          unsigned char  b[sizeof(unsigned short)];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:1134:5:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
  f.open(name.c_str(), std::fstream::in);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:1249:5:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
  f.open(name.c_str(), std::fstream::binary);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:1410:5:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
  f.open(name.c_str(), std::fstream::in);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:1792:5:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
  f.open(name.c_str(), std::fstream::binary);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:1905:5:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
  f.open(name.c_str(), std::fstream::in | std::fstream::binary);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:2180:5:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
  f.open(name.c_str(), std::fstream::in | std::fstream::binary);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:2551:5:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
  f.open(name.c_str(), std::fstream::in);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:2723:5:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
  f.open(name.c_str(), std::fstream::in | std::fstream::binary);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:2955:5:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
  f.open(name.c_str(), std::fstream::binary);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:3489:5:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
  f.open(name.c_str(), std::fstream::binary);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:3650:5:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
  f.open(name.c_str(), std::fstream::binary);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:3876:5:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
  f.open(name.c_str(), std::fstream::in | std::fstream::binary);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:4274:5:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
  f.open(name.c_str(), std::fstream::in | std::fstream::binary);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:4351:5:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
  f.open(name.c_str(), std::fstream::in | std::fstream::binary);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:4537:5:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
  f.open(name.c_str(), std::fstream::in | std::fstream::binary);
data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp:217:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char  which_sm[3] = "SM";
data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp:218:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char  which_lm[3] = "LM";
data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp:219:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char  which_sa[3] = "SA";
data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp:220:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char  which_la[3] = "LA";
data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp:479:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char which_lm[3] = "LM";
data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp:480:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char which_sm[3] = "SM";
data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp:481:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char which_lr[3] = "LR";
data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp:482:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char which_sr[3] = "SR";
data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp:483:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char which_li[3] = "LI";
data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp:484:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char which_si[3] = "SI";
data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp:632:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char which_lm[3] = "LM";
data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp:633:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char which_sm[3] = "SM";
data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp:634:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char which_lr[3] = "LR";
data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp:635:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char which_sr[3] = "SR";
data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp:636:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char which_li[3] = "LI";
data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp:637:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char which_si[3] = "SI";
data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp:1001:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char equed[8];       // extra characters for paranoia
data/armadillo-9.900.1+dfsg/include/armadillo_bits/sp_auxlib_meat.hpp:1006:5:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    char  work[8];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/traits.hpp:34:11:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
  typedef char yes[1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/traits.hpp:35:11:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
  typedef char  no[2];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/traits.hpp:48:11:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
  typedef char yes[1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/traits.hpp:49:11:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
  typedef char  no[2];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/traits.hpp:62:11:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
  typedef char yes[1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/traits.hpp:63:11:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
  typedef char  no[2];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/traits.hpp:1220:11:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
  typedef char yes[1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/traits.hpp:1221:11:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
  typedef char  no[2];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/traits.hpp:1232:11:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
  typedef char yes[1];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/traits.hpp:1233:11:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
  typedef char  no[2];
data/armadillo-9.900.1+dfsg/mex_interface/armaMex.hpp:203:8:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
  std::memcpy(dst_pointer, src_pointer, sizeof(Type)*armaMatrix.n_elem); 
data/armadillo-9.900.1+dfsg/mex_interface/armaMex.hpp:215:8:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
  std::memcpy(dst_pointer, src_pointer, sizeof(double)*armaMatrix.n_elem); 
data/armadillo-9.900.1+dfsg/mex_interface/armaMex.hpp:228:8:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
  std::memcpy(dst_pointer, src_pointer, sizeof(Type)*armaMatrix.n_elem); 
data/armadillo-9.900.1+dfsg/mex_interface/armaMex.hpp:240:8:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
  std::memcpy(dst_pointer, src_pointer, sizeof(double)*armaMatrix.n_elem); 
data/armadillo-9.900.1+dfsg/mex_interface/armaMex.hpp:407:8:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
  std::memcpy(dst_pointer, src_pointer, sizeof(Type)*armaCube.n_elem); 
data/armadillo-9.900.1+dfsg/mex_interface/armaMex.hpp:419:8:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
  std::memcpy(dst_pointer, src_pointer, sizeof(double)*armaCube.n_elem); 
data/armadillo-9.900.1+dfsg/mex_interface/armaMex.hpp:432:8:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
  std::memcpy(dst_pointer, src_pointer, sizeof(Type)*armaCube.n_elem);
data/armadillo-9.900.1+dfsg/mex_interface/armaMex.hpp:444:8:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
  std::memcpy(dst_pointer, src_pointer, sizeof(double)*armaCube.n_elem); 
data/armadillo-9.900.1+dfsg/mex_interface/armaMex.hpp:935:3:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
  char buffer[1024];
data/armadillo-9.900.1+dfsg/mex_interface/armaMex.hpp:961:3:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
  char buffer[1024];
data/armadillo-9.900.1+dfsg/mex_interface/armaMex.hpp:987:3:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
  char buffer[1024];
data/armadillo-9.900.1+dfsg/mex_interface/armaMex.hpp:1013:3:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
  char buffer[1024];
data/armadillo-9.900.1+dfsg/tests/catch.hpp:1537:23:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    struct TrueType { char sizer[1]; };
data/armadillo-9.900.1+dfsg/tests/catch.hpp:1538:24:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
    struct FalseType { char sizer[2]; };
data/armadillo-9.900.1+dfsg/tests/catch.hpp:3131:13:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
            char storage[sizeof(T)];
data/armadillo-9.900.1+dfsg/tests/catch.hpp:6142:14:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
        void open() {
data/armadillo-9.900.1+dfsg/tests/catch.hpp:6236:17:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
                open();
data/armadillo-9.900.1+dfsg/tests/catch.hpp:6282:26:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
                tracker->open();
data/armadillo-9.900.1+dfsg/tests/catch.hpp:6471:16:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
        static char altStackMem[SIGSTKSZ];
data/armadillo-9.900.1+dfsg/tests/catch.hpp:7117:35:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
            char **utf8Argv = new char *[ argc ];
data/armadillo-9.900.1+dfsg/tests/catch.hpp:7631:9:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
        char data[bufferSize];
data/armadillo-9.900.1+dfsg/tests/catch.hpp:7668:15:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
        m_ofs.open( filename.c_str() );
data/armadillo-9.900.1+dfsg/tests/catch.hpp:8908:21:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
                    char asChar[sizeof (int)];
data/armadillo-9.900.1+dfsg/tests/catch.hpp:9550:13:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
            char buffer[maxDoubleSize];
data/armadillo-9.900.1+dfsg/tests/catch.hpp:9557:13:  [2] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf. Risk is low because the source has a constant maximum length.
            sprintf(buffer, "%.3f", duration);
data/armadillo-9.900.1+dfsg/tests/catch.hpp:9784:16:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
        static char line[CATCH_CONFIG_CONSOLE_WIDTH] = {0};
data/armadillo-9.900.1+dfsg/tests/catch.hpp:10364:13:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
            char timeStamp[timeStampSize];
data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_forward.hpp:289:26:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
      #pragma omp atomic read
data/armadillo-9.900.1+dfsg/include/armadillo_bits/arma_rng.hpp:130:25:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
      if(f.good())  { f.read((char*)(&(tmp.b[0])), sizeof(seed_type)); }
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:258:5:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
  f.read( reinterpret_cast<char*>(data_mem), std::streamsize(N_use) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:1290:5:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
  f.read( reinterpret_cast<char *>(x.memptr()), std::streamsize(x.n_elem * uword(sizeof(eT))) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:1832:7:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
    f.read( reinterpret_cast<char *>(x.memptr()), std::streamsize(x.n_elem*sizeof(eT)) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:1958:11:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
        f.read( reinterpret_cast<char*>(tmp.memptr()), std::streamsize(n_elem) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:1977:11:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
        f.read( reinterpret_cast<char *>(tmp.memptr()), std::streamsize(n_elem*2) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:2217:5:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
  f.read( header_mem, std::streamsize(ARMA_MAT_TXT_len) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:2998:7:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
    f.read( reinterpret_cast<char*>(access::rwp(x.values)),      std::streamsize(x.n_nonzero*sizeof(eT))     );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:3002:7:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
    f.read( reinterpret_cast<char*>(access::rwp(x.row_indices)), std::streamsize(x.n_nonzero*sizeof(uword))  );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:3003:7:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
    f.read( reinterpret_cast<char*>(access::rwp(x.col_ptrs)),    std::streamsize((x.n_cols+1)*sizeof(uword)) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:3024:11:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
        f.read( reinterpret_cast<char*>(tmp_a.memptr()), std::streamsize( x.n_nonzero   * sizeof(u32)) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:3025:11:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
        f.read( reinterpret_cast<char*>(tmp_b.memptr()), std::streamsize((x.n_cols + 1) * sizeof(u32)) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:3530:5:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
  f.read( reinterpret_cast<char *>(x.memptr()), std::streamsize(x.n_elem * uword(sizeof(eT))) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:3692:7:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
    f.read( reinterpret_cast<char *>(x.memptr()), std::streamsize(x.n_elem*sizeof(eT)) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:3913:5:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
  f.read( header_mem, std::streamsize(ARMA_CUB_TXT_len) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:4307:5:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
  f.read( raw_header.memptr(), std::streamsize(ARMA_FLD_BIN.length()) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:4405:11:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
        f.read( reinterpret_cast<char*>(tmp.memptr()), std::streamsize(n_elem) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:4426:11:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
        f.read( reinterpret_cast<char *>(tmp.memptr()), std::streamsize(2*n_elem) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:4601:11:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
        f.read( reinterpret_cast<char*>(tmp.memptr()), std::streamsize(n_elem) );
data/armadillo-9.900.1+dfsg/include/armadillo_bits/diskio_meat.hpp:4626:11:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
        f.read( reinterpret_cast<char *>(tmp.memptr()), std::streamsize(2*n_elem) );
data/armadillo-9.900.1+dfsg/tests/catch.hpp:7143:40:  [1] (buffer) getchar:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
                static_cast<void>(std::getchar());
data/armadillo-9.900.1+dfsg/tests/catch.hpp:7148:40:  [1] (buffer) getchar:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
                static_cast<void>(std::getchar());
data/armadillo-9.900.1+dfsg/tests/catch.hpp:8629:50:  [1] (buffer) equal:
  Function does not check the second iterator for over-read conditions
  (CWE-126). This function is often discouraged by most C++ coding standards
  in favor of its safer alternatives provided since C++14. Consider using a
  form of this function that checks the second iterator before potentially
  overflowing it.
        return s.size() >= prefix.size() && std::equal(prefix.begin(), prefix.end(), s.begin());
data/armadillo-9.900.1+dfsg/tests/catch.hpp:8635:50:  [1] (buffer) equal:
  Function does not check the second iterator for over-read conditions
  (CWE-126). This function is often discouraged by most C++ coding standards
  in favor of its safer alternatives provided since C++14. Consider using a
  form of this function that checks the second iterator before potentially
  overflowing it.
        return s.size() >= suffix.size() && std::equal(suffix.rbegin(), suffix.rend(), s.rbegin());

ANALYSIS SUMMARY:

Hits = 1061
Lines analyzed = 223087 in approximately 4.63 seconds (48216 lines/second)
Physical Source Lines of Code (SLOC) = 147179
Hits@level = [0]   0 [1]  25 [2]  83 [3]   2 [4] 951 [5]   0
Hits@level+ = [0+] 1061 [1+] 1061 [2+] 1036 [3+] 953 [4+] 951 [5+]   0
Hits/KSLOC@level+ = [0+] 7.20891 [1+] 7.20891 [2+] 7.03905 [3+] 6.47511 [4+] 6.46152 [5+]   0
Dot directories skipped = 1 (--followdotdir overrides)
Minimum risk level = 1
Not every hit is necessarily a security vulnerability.
There may be other security vulnerabilities; review your code!
See 'Secure Programming HOWTO'
(https://dwheeler.com/secure-programs) for more information.