Date: Wed, 22 Dec 2004 20:31:42 +1100 From: "Chris Martin" <outsidefactor@iinet.net.au> To: <freebsd-newbies@freebsd.org> Subject: Problem resolution techniques Message-ID: <20041222093237.84DB543D49@mx1.FreeBSD.org>
next in thread | raw e-mail | index | archive | help
Hi, I was just looking for some general advice on tracking down issues with compiled software. I am trying to put together a set guidelines for people in my organisation and our partners over escalation and to help establish when issues are not going to be resolved in house in an efficient amount of time. For example, application 'A' is built from ports. It compiles and installs properly, but core dumps on start. Basic resolution steps could be: 1) uninstall, re-download the distfiles and compile again 2) repeat step 1 after checking/removing any make.conf settings that very from those included in generic 3) check an dependant libraries or applications by testing them with other applications What is a good next step, and at which point do we bug the questions mailing list or the code maintainers? Is there a way for non-developers to get useful information about the dump themselves, saving them bothering the developers with yet another "it don't work, here are my system settings and installed apps, please help" e-mails? Thanks, Chris Martin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041222093237.84DB543D49>