dnrops
/
gimp
mirror of https://github.com/GNOME/gimp.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
gimp/app/widgets/gimpcriticaldialog.h

70 lines
2.5 KiB
C
Raw Normal View History

app: new error dialog to backtrace and encourage people to report bugs. GIMP will now try to get a backtrace (on Unix machines only for now, using g_on_error_stack_trace(); for Windows, we will likely have to look into DrMinGW). This is now applied to CRITICAL errors only, which usually means major bugs but are currently mostly hidden unless you run GIMP in terminal. We limit to 3 backtraces, because many CRITICAL typically get into domino effect and cause more CRITICALs (for instance when a g_return*_if_fail() returns too early).
2018-01-23 10:38:46 +08:00
/* GIMP - The GNU Image Manipulation Program
* Copyright (C) 1995 Spencer Kimball and Peter Mattis
*
* gimpcriticaldialog.h
* Copyright (C) 2018 Jehan <jehan@gimp.org>
*
* This program is free software: you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 3 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program. If not, see <http://www.gnu.org/licenses/>.
*/
#ifndef __GIMP_CRITICAL_DIALOG_H__
#define __GIMP_CRITICAL_DIALOG_H__
G_BEGIN_DECLS
#define GIMP_TYPE_CRITICAL_DIALOG (gimp_critical_dialog_get_type ())
#define GIMP_CRITICAL_DIALOG(obj) (G_TYPE_CHECK_INSTANCE_CAST ((obj), GIMP_TYPE_CRITICAL_DIALOG, GimpCriticalDialog))
#define GIMP_CRITICAL_DIALOG_CLASS(klass) (G_TYPE_CHECK_CLASS_CAST ((klass), GIMP_TYPE_CRITICAL_DIALOG, GimpCriticalDialogClass))
#define GIMP_IS_CRITICAL_DIALOG(obj) (G_TYPE_CHECK_INSTANCE_TYPE ((obj), GIMP_TYPE_CRITICAL_DIALOG))
#define GIMP_IS_CRITICAL_DIALOG_CLASS(klass) (G_TYPE_CHECK_CLASS_TYPE ((klass), GIMP_TYPE_CRITICAL_DIALOG))
#define GIMP_CRITICAL_DIALOG_GET_CLASS(obj) (G_TYPE_INSTANCE_GET_CLASS ((obj), GIMP_TYPE_CRITICAL_DIALOG, GimpCriticalDialogClass))
typedef struct _GimpCriticalDialogClass GimpCriticalDialogClass;
struct _GimpCriticalDialog
{
app, tools: add backtrace GUI for crashes as well. This was a bit harder since even though we handle fatal signals, allowing us to do any last action before GIMP crashes, it seems more memory allocation is not allowed at this time. So creating a dialog or simply getting the return output of gdb into the main process is not allowed. What I do instead is running a separate program (gimpdebug) which will take care of creating the new dialog and running a debugger. I still use GimpCriticalDialog code from this separate binary, while I continue to use this widget also within GIMP for non-fatal errors. The reason why we still want to use it within GIMP is that we can bundle several non-fatal errors and backtrace this way (fatal errors don't return anyway) and it's easier to do so when created from the main process.
2018-01-25 21:32:39 +08:00
GtkDialog parent_instance;
app: new error dialog to backtrace and encourage people to report bugs. GIMP will now try to get a backtrace (on Unix machines only for now, using g_on_error_stack_trace(); for Windows, we will likely have to look into DrMinGW). This is now applied to CRITICAL errors only, which usually means major bugs but are currently mostly hidden unless you run GIMP in terminal. We limit to 3 backtraces, because many CRITICAL typically get into domino effect and cause more CRITICALs (for instance when a g_return*_if_fail() returns too early).
2018-01-23 10:38:46 +08:00
GtkWidget *vbox;
GtkWidget *label;
GtkWidget *details;
app, tools: add backtrace GUI for crashes as well. This was a bit harder since even though we handle fatal signals, allowing us to do any last action before GIMP crashes, it seems more memory allocation is not allowed at this time. So creating a dialog or simply getting the return output of gdb into the main process is not allowed. What I do instead is running a separate program (gimpdebug) which will take care of creating the new dialog and running a debugger. I still use GimpCriticalDialog code from this separate binary, while I continue to use this widget also within GIMP for non-fatal errors. The reason why we still want to use it within GIMP is that we can bundle several non-fatal errors and backtrace this way (fatal errors don't return anyway) and it's easier to do so when created from the main process.
2018-01-25 21:32:39 +08:00
gchar *program;
app, tools: various fixes for Win32 build. * Type pid_t is not cross-platform. Just use int instead, and convert it to respective type on each platform. * Get rid of several useless include which should have been removed a few commits ago, when I reimplemented the backtrace function. * Better handle the various macros in gimp_eek() (between G_OS_WIN32, HAVE_EXCHNDL and GIMP_CONSOLE_COMPILATION, but also no_interface and generate_backtrace options, that was a bit messy). * Make gimpdebug now always built, whatever the platform.
2018-01-27 06:47:11 +08:00
gint pid;
app: new error dialog to backtrace and encourage people to report bugs. GIMP will now try to get a backtrace (on Unix machines only for now, using g_on_error_stack_trace(); for Windows, we will likely have to look into DrMinGW). This is now applied to CRITICAL errors only, which usually means major bugs but are currently mostly hidden unless you run GIMP in terminal. We limit to 3 backtraces, because many CRITICAL typically get into domino effect and cause more CRITICALs (for instance when a g_return*_if_fail() returns too early).
2018-01-23 10:38:46 +08:00
};
struct _GimpCriticalDialogClass
{
app, tools: add backtrace GUI for crashes as well. This was a bit harder since even though we handle fatal signals, allowing us to do any last action before GIMP crashes, it seems more memory allocation is not allowed at this time. So creating a dialog or simply getting the return output of gdb into the main process is not allowed. What I do instead is running a separate program (gimpdebug) which will take care of creating the new dialog and running a debugger. I still use GimpCriticalDialog code from this separate binary, while I continue to use this widget also within GIMP for non-fatal errors. The reason why we still want to use it within GIMP is that we can bundle several non-fatal errors and backtrace this way (fatal errors don't return anyway) and it's easier to do so when created from the main process.
2018-01-25 21:32:39 +08:00
GtkDialogClass parent_class;
app: new error dialog to backtrace and encourage people to report bugs. GIMP will now try to get a backtrace (on Unix machines only for now, using g_on_error_stack_trace(); for Windows, we will likely have to look into DrMinGW). This is now applied to CRITICAL errors only, which usually means major bugs but are currently mostly hidden unless you run GIMP in terminal. We limit to 3 backtraces, because many CRITICAL typically get into domino effect and cause more CRITICALs (for instance when a g_return*_if_fail() returns too early).
2018-01-23 10:38:46 +08:00
};
GType gimp_critical_dialog_get_type (void) G_GNUC_CONST;
GtkWidget * gimp_critical_dialog_new (const gchar *title);
app, tools: add backtrace GUI for crashes as well. This was a bit harder since even though we handle fatal signals, allowing us to do any last action before GIMP crashes, it seems more memory allocation is not allowed at this time. So creating a dialog or simply getting the return output of gdb into the main process is not allowed. What I do instead is running a separate program (gimpdebug) which will take care of creating the new dialog and running a debugger. I still use GimpCriticalDialog code from this separate binary, while I continue to use this widget also within GIMP for non-fatal errors. The reason why we still want to use it within GIMP is that we can bundle several non-fatal errors and backtrace this way (fatal errors don't return anyway) and it's easier to do so when created from the main process.
2018-01-25 21:32:39 +08:00
void gimp_critical_dialog_add (GtkWidget *dialog,
app: new error dialog to backtrace and encourage people to report bugs. GIMP will now try to get a backtrace (on Unix machines only for now, using g_on_error_stack_trace(); for Windows, we will likely have to look into DrMinGW). This is now applied to CRITICAL errors only, which usually means major bugs but are currently mostly hidden unless you run GIMP in terminal. We limit to 3 backtraces, because many CRITICAL typically get into domino effect and cause more CRITICALs (for instance when a g_return*_if_fail() returns too early).
2018-01-23 10:38:46 +08:00
const gchar *message,
app, tools: add backtrace GUI for crashes as well. This was a bit harder since even though we handle fatal signals, allowing us to do any last action before GIMP crashes, it seems more memory allocation is not allowed at this time. So creating a dialog or simply getting the return output of gdb into the main process is not allowed. What I do instead is running a separate program (gimpdebug) which will take care of creating the new dialog and running a debugger. I still use GimpCriticalDialog code from this separate binary, while I continue to use this widget also within GIMP for non-fatal errors. The reason why we still want to use it within GIMP is that we can bundle several non-fatal errors and backtrace this way (fatal errors don't return anyway) and it's easier to do so when created from the main process.
2018-01-25 21:32:39 +08:00
const gchar *trace,
gboolean is_fatal,
const gchar *program,
app, tools: various fixes for Win32 build. * Type pid_t is not cross-platform. Just use int instead, and convert it to respective type on each platform. * Get rid of several useless include which should have been removed a few commits ago, when I reimplemented the backtrace function. * Better handle the various macros in gimp_eek() (between G_OS_WIN32, HAVE_EXCHNDL and GIMP_CONSOLE_COMPILATION, but also no_interface and generate_backtrace options, that was a bit messy). * Make gimpdebug now always built, whatever the platform.
2018-01-27 06:47:11 +08:00
gint pid);
app: new error dialog to backtrace and encourage people to report bugs. GIMP will now try to get a backtrace (on Unix machines only for now, using g_on_error_stack_trace(); for Windows, we will likely have to look into DrMinGW). This is now applied to CRITICAL errors only, which usually means major bugs but are currently mostly hidden unless you run GIMP in terminal. We limit to 3 backtraces, because many CRITICAL typically get into domino effect and cause more CRITICALs (for instance when a g_return*_if_fail() returns too early).
2018-01-23 10:38:46 +08:00
G_END_DECLS
#endif /* __GIMP_CRITICAL_DIALOG_H__ */