Roger.
I suspect that some argument variables not being available is the result
of optimization or normal program flow.
Roger Leigh wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Till Straumann <[EMAIL PROTECTED]> writes:
-- snp
(gdb) bt
#0 sbuild_session_setup_chroot (session=0x1004e770,
session_chroot=0x1004bf60, setup_type=SBUILD_CHROOT_SETUP_START,
error=0x7fc04548) at sbuild-session.c:491
#1 0x10014488 in sbuild_session_run (session=0x1004e770, error=0x10054788)
at sbuild-session.c:1064
#2 0x10015304 in sbuild_cclosure_marshal_BOOLEAN__BOXED (closure=0x1004e0e0,
return_value=0x7fc04680, n_param_values=Variable "n_param_values" is not
available.
) at sbuild-marshallers.c:162
If the register holding 'n_param_values' is overwritten/reused at the
time g_type_class_meta_marhal() is called then there is (in general)
no way for the unwinder to resurrect the value it held earlier.
#3 0x0fa7d9dc in g_type_class_meta_marshal (closure=0x1004e770,
return_value=0x7fade680, n_param_values=2, param_values=0x7fade790,
invocation_hint=0x7fade6a0, marshal_data=0x48) at gclosure.c:569
I'm not sure why some variables are "not available", but at least it
can now correctly walk through the stack.
good :-) I submitted PR2029 to the GDB bug database -- please use the
patch from there and not the earlier version I posted yesterday as it
contains an error.
--T.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
