Date: Thu, 13 Jun 2002 20:02:13 -0400 From: Randall Hopper <aa8vb@nc.rr.com> To: Thomas Gellekum <tg@melaten.rwth-aachen.de>, Peter Dufault <dufault@hda.com> Cc: ports@FreeBSD.ORG Subject: Re: Opendx core dumps for me Message-ID: <20020614000213.GB5189@nc.rr.com> In-Reply-To: <20020613113621.A9483@hda.hda.com> <kq4rg7o1pz.fsf@cip12.melaten.rwth-aachen.de> References: <20020607072528.A20647@hda.hda.com> <kq4rg7o1pz.fsf@cip12.melaten.rwth-aachen.de> <20020613113621.A9483@hda.hda.com> <20020607072528.A20647@hda.hda.com> <kq4rg7o1pz.fsf@cip12.melaten.rwth-aachen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Thomas Gellekum: |Peter Dufault <dufault@hda.com> writes: | |> I compiled with debugging and tried to get a backtrace. The stack |> is trashed. Because of that I suspect some pthread misconfiguration. | |I've noticed that both libc_r and libc are linked into dxui, probably |because something along the dependency chain used libtool. My |home-built binaries seem to work fine, though. | |Does ktrace give any clues? Odd. I don't see this either, though I'm not current on FreeBSD versions. Been planning to upgrade to 4.6 when it's released... I'm surprised it's even possible to successfully link with both libc_r and libc. One suggestion. You could try setenv DXROOT /usr/local/dx, fire off dxexec -B -r in one window, and then dx -uionly in another. This would tell you whether you can connect to a running server without the dxexec fork-off (whether this is connect-related or process-related). Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020614000213.GB5189>