Le 19/06/2012 16:20, Alastair McKinstry a écrit :
> While i'm still investigating, _something_ in the sid environment is the
> real culprit and
> I can't assign a bug to it yet until I pin it down. Has anyone seen a
> similar issue elsewhere,
> or got a hint as to how to handle it? I want to make
Hello,
On Tue, 19 Jun 2012 15:11:33 -0700
Josh Triplett wrote:
> Variables in the .bss section will by definition get initialized to 0.
> For example, a C variable defined as "static typename varname;" must
> get initialized to 0, and the compiler and linker will stick it in
> the .bss section e
Andrew Shadura wrote:
> By the way, it might be a good idea to fill .bss section with random
> values intentionally for debug builds to detect non-properly-initialised
> things more effectively :)
Variables in the .bss section will by definition get initialized to 0.
For example, a C variable defi
Hello,
On Tue, 19 Jun 2012 23:03:17 +0200
Bernd Zeimetz wrote:
> Try gcc/g++ 4.6 instead of 4.7. Maybe check if "S-Lang load
> path" (wherever that is stored) is initialized in a sane way. I had a
> similar issue where an integer was 0 all the time - although not
> being initialized with somethi
Hi,
> I've an interesting problem: bug #675125.
> Its a grave bug against slang2, as it breaks jed, (and other things).
> slang2-2.2.14-12+ (in sid) breaks jed for certain locales (C is broken,
> *.UTF-8 look fine);
> but slang2_2.2.14-10 (in testing) looks fine.
>
> The trouble is, while downgr
Hi,
I've an interesting problem: bug #675125.
Its a grave bug against slang2, as it breaks jed, (and other things).
slang2-2.2.14-12+ (in sid) breaks jed for certain locales (C is broken,
*.UTF-8 look fine);
but slang2_2.2.14-10 (in testing) looks fine.
The trouble is, while downgrading to -10 fi
6 matches
Mail list logo
