On Sat, May 28, 2005 at 01:47:11PM -0700, Steve Langasek wrote:
> But it doesn't sound like what you have here is a toolchain bug, it sounds
> like you have a source bug that manifests differently under different
> optimization levels. Could you please try to debug the memory error instead
> of w
On Sat, May 28, 2005 at 12:52:22PM +0200, Enrico Zini wrote:
> I'm maintaining a swig-generated perl module (libdebtags-perl, in
> experimental) which when compiled with -O2 causes the perl program to
> segfault on exit (some memory gets garbled and the destructors choke).
> Compiled with -O0, no p
Hello,
I'm maintaining a swig-generated perl module (libdebtags-perl, in
experimental) which when compiled with -O2 causes the perl program to
segfault on exit (some memory gets garbled and the destructors choke).
Compiled with -O0, no problems.
I've noticed that the perl policy at "4.3. Vendor I
3 matches
Mail list logo
