Re: Remove the Stack Trace...

2000-01-26 Thread Daniel . Egger
On 25 Jan, Marc Lehmann wrote: > I really do not understand this. The stacktrace simply does not work. > Attaching a debugger is much better, but still: the core file a segv > would create would be _far_ more reliable. > I buy the argument that users can do bug reports better with an > automati

Re: Remove the Stack Trace...

2000-01-25 Thread Marc Lehmann
On Tue, Jan 25, 2000 at 06:55:28PM +0100, Raphael Quinet <[EMAIL PROTECTED]> wrote: > There is a difference between having the stack trace and having the > program asking you if you want a stack trace... The latter is more > useful for developers because you can also choose to start gdb and Sorr

Re: Remove the Stack Trace...

2000-01-25 Thread Glyph Lefkowitz
On Tue, 25 Jan 2000, Marc Lehmann wrote: > BTW: the stacktrace option has never worked on my machine(s), unless you > call "endless loop" working. Also, I could never get out of that signal > handler. Gimp just started to suck 100% cpu time when I tried to "e"xit. > > I doubt that this thing i

Re: Remove the Stack Trace...

2000-01-25 Thread Raphael Quinet
On Tue, 25 Jan 2000, Marc Lehmann <[EMAIL PROTECTED]> wrote: > On Mon, Jan 24, 2000 at 11:05:35AM -0500, Glyph Lefkowitz <[EMAIL PROTECTED]> >wrote: > > Since the only advantage of this is the stack-trace for non-developers, > > The consensus was to remove it in release versions. So if the only

Re: Remove the Stack Trace...

2000-01-25 Thread Marc Lehmann
On Mon, Jan 24, 2000 at 06:31:24PM +0100, Raphael Quinet <[EMAIL PROTECTED]> wrote: > Any suggestions for the name of the new option? It could be something > like "--disable-stack-trace" or "--disable-crash-query", assuming that That option must propagate to the plug-ins, btw, so maybe an enviro

Re: Remove the Stack Trace...

2000-01-25 Thread Marc Lehmann
On Mon, Jan 24, 2000 at 11:05:35AM -0500, Glyph Lefkowitz <[EMAIL PROTECTED]> wrote: > Since the only advantage of this is the stack-trace for non-developers, The consensus was to remove it in release versions. So if the only advantage is for non-developers, why not remove it altogether? (It mu

Re: Remove the Stack Trace...

2000-01-25 Thread Jens Lautenbacher
Manish Singh <[EMAIL PROTECTED]> writes: > > How about --enable-stack-trace=[yes/no/query] and set it to query by default. > We'll set the default to no for stable releases. > > This should just set the default setting that gimp uses at runtime. There > should be runtime options that parallel to

Re: Remove the Stack Trace...

2000-01-24 Thread Daniel . Egger
On 24 Jan, Raphael Quinet wrote: > Any suggestions for the name of the new option? It could be something > > like "--disable-stack-trace" or "--disable-crash-query", assuming > that the default behaviour would be to have it enabled in unstable > releases. Note that I also support the idea posted

Re: Remove the Stack Trace...

2000-01-24 Thread Manish Singh
On Mon, Jan 24, 2000 at 06:31:24PM +0100, Raphael Quinet wrote: > On Mon, 24 Jan 2000, Austin Donnelly <[EMAIL PROTECTED]> wrote: > > On Monday, 24 Jan 2000, Glyph Lefkowitz wrote: > > > Since the only advantage of this is the stack-trace for non-developers, > > > why don't we just have it dump st

Re: Remove the Stack Trace...

2000-01-24 Thread Daniel . Egger
On 24 Jan, Jens Lautenbacher wrote: > I would like to kindly suggest that we at least give a configure > option to avoid the stacktrace stuff that happens when gimp crashes. > I'm currently developping a distributed perlfu server and it would > make life much much easier if gimp would simply cr

Re: Remove the Stack Trace...

2000-01-24 Thread Sven Neumann
Hi jtl, > I would like to kindly suggest that we at least give a configure > option to avoid the stacktrace stuff that happens when gimp crashes. > > > I also remember having big problems with a segfaultet gimp started > from the gnome panel (or any other non-shell commandline means) and > gimp

Re: Remove the Stack Trace...

2000-01-24 Thread Raphael Quinet
On Mon, 24 Jan 2000, Austin Donnelly <[EMAIL PROTECTED]> wrote: > On Monday, 24 Jan 2000, Glyph Lefkowitz wrote: > > Since the only advantage of this is the stack-trace for non-developers, > > why don't we just have it dump stack, then die, by default. > > This sounds sensible, but also add a che

Re: Remove the Stack Trace...

2000-01-24 Thread Austin Donnelly
On Monday, 24 Jan 2000, Glyph Lefkowitz wrote: > Since the only advantage of this is the stack-trace for non-developers, > why don't we just have it dump stack, then die, by default. This sounds sensible, but also add a check on istty(stdout) being true. No point taking forever doing a backtrac

Re: Remove the Stack Trace...

2000-01-24 Thread Glyph Lefkowitz
On 24 Jan 2000, Jens Lautenbacher wrote: > I also remember having big problems with a segfaultet gimp started > from the gnome panel (or any other non-shell commandline means) and > gimp crashing while still having grabed the mouse. YES. Especially with the grabbed mouse. I am casting my vot