Re: how to get backtrace on warnings?
- From: Iain <iain ximian com>
- To: jrb redhat com
- Cc: Dave Morse <dm-gtk bomberlan net>, gtk-app-devel-list gnome org
- Subject: Re: how to get backtrace on warnings?
- Date: 20 May 2001 01:21:24 -0400
On 19 May 2001 22:26:26 -0400, jrb redhat com wrote:
Dave Morse <dm-gtk bomberlan net> writes:
I'm trying to figure out which line of code, of roughly 97 million, is
responsible for things like this:
Gdk-ERROR **: BadValue (integer parameter out of range for operation)
serial 5170 error_code 2 request_code 130 minor_code 9
I'd like to get a backtrace or something. I tried running the app with
"--sync --g-fatal-warnings", then getting gdb to break on the call of the
function "exit", but gdb refuses to break on exit. I tried breaking
gtk_exit, but its not called. Ideas?
Break on g_log.
Or if it's an X error like that one looks, try breaking on gdk_x_error
i
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]