> "Jim" == James E Wilson <[EMAIL PROTECTED]> writes:
Jim> The interface between the front ends and cgraph really needs to be
Jim> worked out here. Currently, the C and C++ front ends are calling some
Jim> cgraph functions in different orders, and we are having lots of debug
Jim> related prob
On Wed, 2005-08-24 at 12:33 -0700, James E Wilson wrote:
> Nick Clifton wrote:
> > The reason for this behaviour is that the debug information is being
> > written out before the variables have been fully resolved. In
> > particular DECL_SET() for the second and third observer functions is
>
Nick Clifton wrote:
> The reason for this behaviour is that the debug information is being
> written out before the variables have been fully resolved. In
> particular DECL_SET() for the second and third observer functions is
> NULL when the debug info is generated, which is why they are b
>
> Hi Guys,
>
> There is a problem with unit-at-a-time compilation and DWARF debug
> info generation. Consider this small test case which has been
> derived from GDB's observer.c source file:
There was even more issues with uninitialized variables a month ago.
This was all caused by Mark
Hi Guys,
There is a problem with unit-at-a-time compilation and DWARF debug
info generation. Consider this small test case which has been
derived from GDB's observer.c source file:
int observer_test_first_observer = 0;
int observer_test_second_observer = 0;
int observer_test_th
