On Fri, 07 Nov 2014 08:49:34 -0500 Steven Schveighoffer via Digitalmars-d-learn <digitalmars-d-learn@puremagic.com> wrote:
> On 11/6/14 11:43 PM, ketmar via Digitalmars-d-learn wrote: > > On Thu, 06 Nov 2014 22:45:23 -0500 > > Steven Schveighoffer via Digitalmars-d-learn > > <digitalmars-d-learn@puremagic.com> wrote: > > > >> In an environment that you don't control, the default behavior is likely > >> to print "Segmentation Fault" and exit. No core dump, no nothing. > >> > >> This leads to unhelpful bug reports, and seeing if you can get your > >> client to "try to make it happen again with this debug build, or with > >> the shell set up to make a core dump". > > > > README file, prerequisites: "please, turn on coredump feature if you > > plan to send bug reports. thank you." > > This doesn't help. We must live in the real world with real customers :) i do. this really helps when clients wants their problem to be solved. and if they doesn't, it's sufficient to answer like "thank you for your report, we are working on it" (and then dumping that "report" to /dev/null). this works perfectly.
signature.asc
Description: PGP signature
