Segfault with gcc4 and LD_PRELOAD (was: Need help to fill bug report (gcc 4.0.1 and above))

2005-08-29 Thread Mathieu Malaterre
in $ cvs -d:pserver:[EMAIL PROTECTED]:2401/cvsroot/VTK co VTK $ mkdir VTK-gcc $ cd VTK-gcc $ cmake ../VTK $ make ... Thanks for any advice on tracking down this bug, Mathieu Mathieu Malaterre wrote: Hello, I have currently a reproducable seg fault from an exe produced by gcc 4.0.1 (*). It do

Need help to fill bug report (gcc 4.0.1 and above)

2005-08-28 Thread Mathieu Malaterre
Hello, I have currently a reproducable seg fault from an exe produced by gcc 4.0.1 (*). It does not appear using gcc 2.95, 3.2, 3.3, 3.4. If I run it throught gdb I get: 0x402814b1 in __gnu_cxx::__pool::_M_reclaim_block () from /usr/lib/libstdc++.so.6 (gdb) bt #0 0x402814b1 in __gnu_cxx::_

Re: Surprising behavior of __attribute__((deprecated)) in ctor

2005-07-24 Thread Mathieu Malaterre
mrs $ g++-3.3 t7.cc t7.cc: In constructor `A::A(int)': t7.cc:11: warning: `A' is deprecated (declared at t7.cc:9) t7.cc: In constructor `A::A(int)': t7.cc:11: warning: `A' is deprecated (declared at t7.cc:9) Yup, right testcase... To support Panther I defined a MACRO: # if defined(__GNUC__)

Surprising behavior of __attribute__((deprecated)) in ctor

2005-07-23 Thread Mathieu Malaterre
Hello, I have quite a surpising behavior with gcc when compiling the following code (*). Here is the output: $ g++ deprecated.cxx /tmp deprecated.cxx: In constructor `A::A(int)': deprecated.cxx:11: warning: `A' is deprecated (declared at deprecated.cxx:9)

Re: c/c++ validator

2005-06-18 Thread Mathieu Malaterre
Gabriel Dos Reis wrote: Tommy Vercetti <[EMAIL PROTECTED]> writes: | On Sunday 19 June 2005 03:03, you wrote: | > Tommy Vercetti <[EMAIL PROTECTED]> writes: | > | On Sunday 19 June 2005 00:32, you wrote: | > | > Something like: | > | > | > | > http://www.cs.rpi.edu/~gregod/STLlint/STLlint.html |

Re: c/c++ validator

2005-06-18 Thread Mathieu Malaterre
Something like: http://www.cs.rpi.edu/~gregod/STLlint/STLlint.html HTH Mathieu Tommy Vercetti wrote: Hi folks I would like to ask you about source validation software. Software that runs trough source code, and attempts to find any possible memory leaks, and other problems. Is there anythin

Re: ld: common symbols not allowed with MH_DYLIB output format with the -multi_module option

2005-06-10 Thread Mathieu Malaterre
On Jun 10, 2005, at 3:45 PM, Mike Stump wrote: I'd put this more simply... On Monday, June 6, 2005, at 02:06 PM, Mathieu Malaterre wrote: I have a question about a valid C code. I am trying to compile the following code in MacOSX (*). I don't understand what the problem is?

Re: ld: common symbols not allowed with MH_DYLIB output

2005-06-06 Thread Mathieu Malaterre
Sam, Since you seems very knowledgable why does the error desepear when I initialize the structure ? int bar [ 4 * 256 ] = { 0,1,2, ... }; I did not changed nor any compiler option, neither any declaration. I still cannot see the difference in between those two, since the declaration

ld: common symbols not allowed with MH_DYLIB output format with the -multi_module option

2005-06-06 Thread Mathieu Malaterre
Hello, I have a question about a valid C code. I am trying to compile the following code in MacOSX (*). I don't understand what the problem is ? Could someone please explain me what is going on ? Since I declare the variable with extern I should not need to pass -fno-common, right ? Thank