看板 FB_current 關於我們 聯絡資訊
--Sig_//Cv8fOTUy+ggz/rZmBaBywj Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Mon, 23 Jun 2014 17:22:25 +0200 Dimitry Andric <dim@FreeBSD.org> schrieb: > On 23 Jun 2014, at 16:31, O. Hartmann <ohartman@zedat.fu-berlin.de> wrote: > > Am Sun, 22 Jun 2014 10:10:04 -0700 > > Adrian Chadd <adrian@freebsd.org> schrieb: > >> When they segfault, where do they segfault? > ... > > GIMP, LaTeX work, nothing special, but a bit memory consuming regrading= GIMP) I tried > > updating the ports tree and surprisingly the tree is left over in a unc= lean condition > > while /usr/bin/svn segfault (on console: pid 18013 (svn), uid 0: exited= on signal 11 > > (core dumped)). > >=20 > > Using /usr/local/bin/svn, which is from the devel/subversion port, perf= orms well, > > while FreeBSD 11's svn contribution dies as described. It did not hours= ago! >=20 > I think what Adrian meant was: can you run svn (or another crashing > program) in gdb, and post a backtrace? Or maybe run ktrace, and see > where it dies? >=20 > Alternatively, put a core dump and the executable (with debug info) in a > tarball, and upload it somewhere, so somebody else can analyze it. >=20 > -Dimitry >=20 It's me again, with the same weird story. After a couple of days silence, the mysterious entity in my computer is bac= k. This time it is again a weird compiler message of failure (trying to buildworld): [...] c++ -O2 -pipe -O3 -O3 -I/usr/src/lib/clang/libllvmsupport/../../../contrib= /llvm/include -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/inclu= de -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I. -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/i= nclude -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MA= CROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=3D\"x86_64-unknown-freebs= d11.0\" -DLLVM_HOST_TRIPLE=3D\"x86_64-unknown-freebsd11.0\" -DDEFAULT_SYSROOT=3D\"\" -Qunused-arguments -I/usr/obj/usr/src/tmp/legacy/usr/include -std=3Dc++11 -= fno-exceptions -fno-rtti -Wno-c++11-extensions -c /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Host= ..cpp -o Host.o --- GraphWriter.o --- In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Gr= aphWriter.cpp:14: /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/i= nclude/llvm/Support/GraphWriter.h:269:10: error: use of undeclared identifier 'DOD'; did you mean 'DOT'? O << DOD::EscapeString(Label); ^~~ DOT /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include/llvm/Su= pport/GraphWriter.h:35:11: note: 'DOT' declared here namespace DOT { // Private functions... ^ 1 erro= r generated. *** [GraphWriter.o] Error code 1 Well, in the past I saw many of those messages, especially not found labels= of routines in shared objects/libraries or even those "funny" misspelled messages shown= above. I can not reproduce them after a reboot, but as long as the system is runni= ng with this error occured, it is sticky. So in order to compile the OS successfully, I = reboot. Does anyone have an idea what this could be? Since it affects at the moment= only one machine (the other CoreDuo has been retired in the meanwhile), it feels a b= it like a miscompilation on a certain type of CPU. Thanks for your patience, Oliver --Sig_//Cv8fOTUy+ggz/rZmBaBywj Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJTsrKvAAoJEOgBcD7A/5N8AsUH/RHQKWrbyt2o68WTLlNpUxI8 TYMp9rUeKyVJUtthCjcXYNQ4OMX2rKEyc/E0nGRQZFHvZed/793rXnhHX7tS39dS MmFMy9LEE3kra4RYPE944A+CZ9A3EW6S+fhQcWlwGDKKzrhkl5yUGR0cexTEeODC ejo0GNIf8r4hyEf77QwrIRLimu7TwNNJG3PQLnRyaJOepFQXJOEPqX5a5AR7wFsM al+WAlOGiuDZHnFY4eDDj+6ztlTYUJrdvZ0U5/jMffmbV/pzFn0T1VagYdEL1wfx FpDVqKkW7Cldx79IJi6qVCKFgay+JWcNE0Y53njaSgSdeJ1Vlz47uYWRPXz2HVo= =Tsta -----END PGP SIGNATURE----- --Sig_//Cv8fOTUy+ggz/rZmBaBywj--