Date: Tue, 1 Jul 2014 14:48:09 +0000 From: "Rang, Anton" <anton.rang@isilon.com> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de>, Dimitry Andric <dim@FreeBSD.org> Cc: Adrian Chadd <adrian@freebsd.org>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: RE: [CURRENT]: weird memory/linker problem? Message-ID: <F21EDC44C64DB34B90AF485AC3CEDD4B3539868C@MX104CL01.corp.emc.com> In-Reply-To: <20140701150755.548ed6b9.ohartman@zedat.fu-berlin.de> References: <20140622165639.17a1ba1e.ohartman@zedat.fu-berlin.de> <CAJ-Vmok0Oh6XGe62acXE-82pTmEaouibd1GqDT0pCo8P6x6Hog@mail.gmail.com> <20140623163115.03bdd675.ohartman@zedat.fu-berlin.de> <F427210C-D7A9-499F-AFF9-C0B29CC6D51B@FreeBSD.org> <20140701150755.548ed6b9.ohartman@zedat.fu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
DOT =3D> DOD 444F54 =3D> 444F44 That's a single-bit flip. Bad memory, perhaps? Anton -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freeb= sd.org] On Behalf Of O. Hartmann Sent: Tuesday, July 01, 2014 8:08 AM To: Dimitry Andric Cc: Adrian Chadd; FreeBSD CURRENT Subject: Re: [CURRENT]: weird memory/linker problem? 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=20 > > regrading GIMP) I tried updating the ports tree and surprisingly the=20 > > tree is left over in a unclean condition while /usr/bin/svn segfault=20 > > (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,=20 > > performs well, while FreeBSD 11's svn contribution dies as described. I= t 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=20 > where it dies? >=20 > Alternatively, put a core dump and the executable (with debug info) in=20 > 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 bui= ldworld): [...] c++ -O2 -pipe -O3 -O3=20 c++ -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-f= reebsd11.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/libllv= msupport/../../../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::Es= capeString(Label); ^~~ DOT /usr/src/lib/clang/libllvmsupport/../../../contr= ib/llvm/include/llvm/Support/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 m= essages 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 suc= cessfully, 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 bit like a miscompilation on a certain type of CPU. Thanks for your patience, Oliver
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F21EDC44C64DB34B90AF485AC3CEDD4B3539868C>