procyberian/gimp
2
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/gimp.git synced 2025-07-04 01:43:24 +00:00
Code Issues 1 Projects 1 Releases Packages Wiki Activity Actions
gimp/app/core/gimpbacktrace-none.c

127 lines
2.6 KiB
C
Raw Normal View History

app: add GimpBacktrace GimpBacktrace provides an interface for creating and traversing multi-threaded backtraces, as well as querying symbol information. While we already have some backtrace functionality, it relies on external tools for the most part, and as such is rather expensive, and is only meant for producing opaque backtraces. GimpBacktrace, on the other hand, is meant to be relatively cheap (we're going to use it for profiling,) and allow inspection of the backtrace data. In the future, it might make sense to replace some, or all, of the other backtrace functions with GimpBacktrace. GimpBacktrace currently only supports Linux. By default, it uses dladdr() to query symbol information, which is somewhat limited (in particular, it doesn't work for static functions.) When libunwind is installed, GimpBacktrace uses it to get more complete symbol information. libunwind is currently an optional dependency, but it might make sense to promote it to a mandatory, or opt-out, dependency, as it's lightweight and widely available. On other platforms, the GimpBacktrace interface can still be used, but it always returns NULL backtraces.
2018-09-02 01:15:35 -04:00
/* GIMP - The GNU Image Manipulation Program
* Copyright (C) 1995-1999 Spencer Kimball and Peter Mattis
*
app: minor cleanup in GimpBacktrace
2018-09-02 09:08:09 -04:00
* gimpbacktrace-none.c
app: add GimpBacktrace GimpBacktrace provides an interface for creating and traversing multi-threaded backtraces, as well as querying symbol information. While we already have some backtrace functionality, it relies on external tools for the most part, and as such is rather expensive, and is only meant for producing opaque backtraces. GimpBacktrace, on the other hand, is meant to be relatively cheap (we're going to use it for profiling,) and allow inspection of the backtrace data. In the future, it might make sense to replace some, or all, of the other backtrace functions with GimpBacktrace. GimpBacktrace currently only supports Linux. By default, it uses dladdr() to query symbol information, which is somewhat limited (in particular, it doesn't work for static functions.) When libunwind is installed, GimpBacktrace uses it to get more complete symbol information. libunwind is currently an optional dependency, but it might make sense to promote it to a mandatory, or opt-out, dependency, as it's lightweight and widely available. On other platforms, the GimpBacktrace interface can still be used, but it always returns NULL backtraces.
2018-09-02 01:15:35 -04:00
* Copyright (C) 2018 Ell
*
* 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 <https://www.gnu.org/licenses/>.
*/
#include "config.h"
app: more GimpBacktrace tidying ... in preparation for the Windows backend.
2018-09-03 15:29:20 -04:00
#include <gio/gio.h>
app: add GimpBacktrace GimpBacktrace provides an interface for creating and traversing multi-threaded backtraces, as well as querying symbol information. While we already have some backtrace functionality, it relies on external tools for the most part, and as such is rather expensive, and is only meant for producing opaque backtraces. GimpBacktrace, on the other hand, is meant to be relatively cheap (we're going to use it for profiling,) and allow inspection of the backtrace data. In the future, it might make sense to replace some, or all, of the other backtrace functions with GimpBacktrace. GimpBacktrace currently only supports Linux. By default, it uses dladdr() to query symbol information, which is somewhat limited (in particular, it doesn't work for static functions.) When libunwind is installed, GimpBacktrace uses it to get more complete symbol information. libunwind is currently an optional dependency, but it might make sense to promote it to a mandatory, or opt-out, dependency, as it's lightweight and widely available. On other platforms, the GimpBacktrace interface can still be used, but it always returns NULL backtraces.
2018-09-02 01:15:35 -04:00
#include "gimpbacktrace-backend.h"
#ifdef GIMP_BACKTRACE_BACKEND_NONE
#include "core-types.h"
#include "gimpbacktrace.h"
/* public functions */
app: more GimpBacktrace tidying ... in preparation for the Windows backend.
2018-09-03 15:29:20 -04:00
void
app: add GimpBacktrace GimpBacktrace provides an interface for creating and traversing multi-threaded backtraces, as well as querying symbol information. While we already have some backtrace functionality, it relies on external tools for the most part, and as such is rather expensive, and is only meant for producing opaque backtraces. GimpBacktrace, on the other hand, is meant to be relatively cheap (we're going to use it for profiling,) and allow inspection of the backtrace data. In the future, it might make sense to replace some, or all, of the other backtrace functions with GimpBacktrace. GimpBacktrace currently only supports Linux. By default, it uses dladdr() to query symbol information, which is somewhat limited (in particular, it doesn't work for static functions.) When libunwind is installed, GimpBacktrace uses it to get more complete symbol information. libunwind is currently an optional dependency, but it might make sense to promote it to a mandatory, or opt-out, dependency, as it's lightweight and widely available. On other platforms, the GimpBacktrace interface can still be used, but it always returns NULL backtraces.
2018-09-02 01:15:35 -04:00
gimp_backtrace_init (void)
app: more GimpBacktrace tidying ... in preparation for the Windows backend.
2018-09-03 15:29:20 -04:00
{
}
gboolean
gimp_backtrace_start (void)
app: add GimpBacktrace GimpBacktrace provides an interface for creating and traversing multi-threaded backtraces, as well as querying symbol information. While we already have some backtrace functionality, it relies on external tools for the most part, and as such is rather expensive, and is only meant for producing opaque backtraces. GimpBacktrace, on the other hand, is meant to be relatively cheap (we're going to use it for profiling,) and allow inspection of the backtrace data. In the future, it might make sense to replace some, or all, of the other backtrace functions with GimpBacktrace. GimpBacktrace currently only supports Linux. By default, it uses dladdr() to query symbol information, which is somewhat limited (in particular, it doesn't work for static functions.) When libunwind is installed, GimpBacktrace uses it to get more complete symbol information. libunwind is currently an optional dependency, but it might make sense to promote it to a mandatory, or opt-out, dependency, as it's lightweight and widely available. On other platforms, the GimpBacktrace interface can still be used, but it always returns NULL backtraces.
2018-09-02 01:15:35 -04:00
{
return FALSE;
}
void
app: more GimpBacktrace tidying ... in preparation for the Windows backend.
2018-09-03 15:29:20 -04:00
gimp_backtrace_stop (void)
app: add GimpBacktrace GimpBacktrace provides an interface for creating and traversing multi-threaded backtraces, as well as querying symbol information. While we already have some backtrace functionality, it relies on external tools for the most part, and as such is rather expensive, and is only meant for producing opaque backtraces. GimpBacktrace, on the other hand, is meant to be relatively cheap (we're going to use it for profiling,) and allow inspection of the backtrace data. In the future, it might make sense to replace some, or all, of the other backtrace functions with GimpBacktrace. GimpBacktrace currently only supports Linux. By default, it uses dladdr() to query symbol information, which is somewhat limited (in particular, it doesn't work for static functions.) When libunwind is installed, GimpBacktrace uses it to get more complete symbol information. libunwind is currently an optional dependency, but it might make sense to promote it to a mandatory, or opt-out, dependency, as it's lightweight and widely available. On other platforms, the GimpBacktrace interface can still be used, but it always returns NULL backtraces.
2018-09-02 01:15:35 -04:00
{
}
GimpBacktrace *
gimp_backtrace_new (gboolean include_current_thread)
{
return NULL;
}
void
gimp_backtrace_free (GimpBacktrace *backtrace)
{
g_return_if_fail (backtrace == NULL);
}
gint
gimp_backtrace_get_n_threads (GimpBacktrace *backtrace)
{
g_return_val_if_reached (0);
}
guintptr
gimp_backtrace_get_thread_id (GimpBacktrace *backtrace,
gint thread)
{
g_return_val_if_reached (0);
}
const gchar *
gimp_backtrace_get_thread_name (GimpBacktrace *backtrace,
gint thread)
{
g_return_val_if_reached (NULL);
}
app, tools: add "running" thread attribute to GimpBacktrace/performance-log The "running" attribute (readable through gimp_backtrace_is_thread_running(), and recorded in the performance log) specifies if the thread was in a running or suspended state at the time the backtrace was taken. It is accurate on Linux, but only approximated on Windows. Adapt the performance-log-expand.py tool to maintain this attribute (and any future thread attributes we might add).
2018-09-03 18:13:16 -04:00
gboolean
gimp_backtrace_is_thread_running (GimpBacktrace *backtrace,
gint thread)
{
g_return_val_if_reached (FALSE);
}
app: add GimpBacktrace GimpBacktrace provides an interface for creating and traversing multi-threaded backtraces, as well as querying symbol information. While we already have some backtrace functionality, it relies on external tools for the most part, and as such is rather expensive, and is only meant for producing opaque backtraces. GimpBacktrace, on the other hand, is meant to be relatively cheap (we're going to use it for profiling,) and allow inspection of the backtrace data. In the future, it might make sense to replace some, or all, of the other backtrace functions with GimpBacktrace. GimpBacktrace currently only supports Linux. By default, it uses dladdr() to query symbol information, which is somewhat limited (in particular, it doesn't work for static functions.) When libunwind is installed, GimpBacktrace uses it to get more complete symbol information. libunwind is currently an optional dependency, but it might make sense to promote it to a mandatory, or opt-out, dependency, as it's lightweight and widely available. On other platforms, the GimpBacktrace interface can still be used, but it always returns NULL backtraces.
2018-09-02 01:15:35 -04:00
gint
gimp_backtrace_find_thread_by_id (GimpBacktrace *backtrace,
guintptr thread_id,
gint thread_hint)
{
g_return_val_if_reached (-1);
}
gint
gimp_backtrace_get_n_frames (GimpBacktrace *backtrace,
gint thread)
{
g_return_val_if_reached (0);
}
app: in gimpbacktrace-none.c, fix gimp_backtrace_get_frame_address()
2018-09-02 13:14:49 -04:00
guintptr
app: add GimpBacktrace GimpBacktrace provides an interface for creating and traversing multi-threaded backtraces, as well as querying symbol information. While we already have some backtrace functionality, it relies on external tools for the most part, and as such is rather expensive, and is only meant for producing opaque backtraces. GimpBacktrace, on the other hand, is meant to be relatively cheap (we're going to use it for profiling,) and allow inspection of the backtrace data. In the future, it might make sense to replace some, or all, of the other backtrace functions with GimpBacktrace. GimpBacktrace currently only supports Linux. By default, it uses dladdr() to query symbol information, which is somewhat limited (in particular, it doesn't work for static functions.) When libunwind is installed, GimpBacktrace uses it to get more complete symbol information. libunwind is currently an optional dependency, but it might make sense to promote it to a mandatory, or opt-out, dependency, as it's lightweight and widely available. On other platforms, the GimpBacktrace interface can still be used, but it always returns NULL backtraces.
2018-09-02 01:15:35 -04:00
gimp_backtrace_get_frame_address (GimpBacktrace *backtrace,
gint thread,
gint frame)
{
app: in gimpbacktrace-none.c, fix gimp_backtrace_get_frame_address()
2018-09-02 13:14:49 -04:00
g_return_val_if_reached (0);
app: add GimpBacktrace GimpBacktrace provides an interface for creating and traversing multi-threaded backtraces, as well as querying symbol information. While we already have some backtrace functionality, it relies on external tools for the most part, and as such is rather expensive, and is only meant for producing opaque backtraces. GimpBacktrace, on the other hand, is meant to be relatively cheap (we're going to use it for profiling,) and allow inspection of the backtrace data. In the future, it might make sense to replace some, or all, of the other backtrace functions with GimpBacktrace. GimpBacktrace currently only supports Linux. By default, it uses dladdr() to query symbol information, which is somewhat limited (in particular, it doesn't work for static functions.) When libunwind is installed, GimpBacktrace uses it to get more complete symbol information. libunwind is currently an optional dependency, but it might make sense to promote it to a mandatory, or opt-out, dependency, as it's lightweight and widely available. On other platforms, the GimpBacktrace interface can still be used, but it always returns NULL backtraces.
2018-09-02 01:15:35 -04:00
}
gboolean
app: rename gimp_backtrace_get_symbol_info() to ..._get_address_info() This function returns information about the given address, which is currently mostly limited to the corresponding symbol information, but we might want to add address-specific information in the future, such as a line number.
2018-09-02 13:22:27 -04:00
gimp_backtrace_get_address_info (guintptr address,
GimpBacktraceAddressInfo *info)
app: add GimpBacktrace GimpBacktrace provides an interface for creating and traversing multi-threaded backtraces, as well as querying symbol information. While we already have some backtrace functionality, it relies on external tools for the most part, and as such is rather expensive, and is only meant for producing opaque backtraces. GimpBacktrace, on the other hand, is meant to be relatively cheap (we're going to use it for profiling,) and allow inspection of the backtrace data. In the future, it might make sense to replace some, or all, of the other backtrace functions with GimpBacktrace. GimpBacktrace currently only supports Linux. By default, it uses dladdr() to query symbol information, which is somewhat limited (in particular, it doesn't work for static functions.) When libunwind is installed, GimpBacktrace uses it to get more complete symbol information. libunwind is currently an optional dependency, but it might make sense to promote it to a mandatory, or opt-out, dependency, as it's lightweight and widely available. On other platforms, the GimpBacktrace interface can still be used, but it always returns NULL backtraces.
2018-09-02 01:15:35 -04:00
{
return FALSE;
}
#endif /* GIMP_BACKTRACE_BACKEND_NONE */
Reference in a new issue Copy permalink