On Nov 19, 2019, at 7:06 PM, Dennis Clarke <dcla...@blastwave.org> wrote: > > gmake: *** [Makefile:1256: tcltest] Segmentation fault (core dumped)
… > CC=/opt/bw/gcc9/bin/gcc You’re using a nonstandard compiler (i.e. not provided by Red Hat) with non-default options, but it’s SQLite at fault here? Seems like quite a leap of logic to me. Where did you get that compiler binary? Or did you build it yourself? I ask because a Google search for “/opt/bw/gcc9” turns up almost nothing. I get only three results, one of which is your prior thread here. Three! > -march=k8 -mtune=k8 That’s kind of an old CPU. Maybe try -mtune=native instead, unless you need the resulting binaries to be broadly portable. Your symptom would be explained if you aren’t actually running this binary on a K8 compatible CPU. If you don’t like -mtune=native, try dropping this and the -march options entirely. If the symptom goes away, you’re building the binary for a CPU you don’t have. And yes, this sort of problem can be code-dependent. Some code will build and run under the wrong -mtune or -march options, where other code won’t, because the latter code causes the compiler to generate code that the other code doesn’t. Code coverage can also play into it: I built binaries with the wrong option not long ago that ran and showed their help screens, but which core dumped when asked to do real work. Changing the -march option fixed it. > -malign-double -mpc80 Those are both the default on GCC with 64-bit CPUs. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
