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
automatic
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
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 advantage
Hi Folks,
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 crash without hanging
still around
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
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 stack, then
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
