Re: Variables not available
- From: Scott Bronson <bronson rinspin com>
- To: Rod Butcher <rbutcher hyenainternet com>
- Cc: gnome-bugsquad gnome org
- Subject: Re: Variables not available
- Date: Wed, 25 Jan 2006 00:41:16 -0500
Your compiler might be optimizing the variable away. Are you using -O2
or higher?
Try recompiling with -O0 maybe?
On Wed, 2006-01-25 at 14:28 +1100, Rod Butcher wrote:
> I get very many examples of variable not available (e.g. evolution
> example below) when I try to get stack traces using either "thread apply
> all bt" or just "bt". Yet I understand that if I build from cvs it
> should build in debugging info - I understand -g is most important,
> correct ? I tried manually setting -g and still get mostly "not
> available". Am I doing something wrong or is this inevitable and if so why ?
>
> #4 0xb6b48e96 in signal_emit_unlocked_R (node=Variable "node" is not
> available.
> ) at gsignal.c:2438
>
> thanks
> Rod
> ------------------------------------------------------------------------------------------------
> http://www.distributedcomputing.info - find out how to make your
> computer work for the community
> _______________________________________________
> Gnome-bugsquad mailing list
> Gnome-bugsquad gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-bugsquad
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]