Processing commands for [EMAIL PROTECTED]:
> reassign 117513 openc++
Bug#117513: openc++: segfault or "Error 139" compiling anything, even empty file
Bug reassigned from package `g++-2.95' to `openc++'.
> thanks
Stopping processing here.
Please contact me if you ne
reassign 117513 openc++
thanks
On Wed, Nov 14, 2001 at 12:21:27AM -0800, Robert de Forest wrote:
> > 1. gets a char* pointer from a func that allocates it with "char*
> > result = new char[...]" (and although it does not test the return
> > value from "new", this is not the problem here - added ch
On Wed, Nov 14, 2001 at 12:21:27AM -0800, Robert de Forest wrote:
> > I higly suspect this to be a g++ bug. I tried with g++ 3.0, but it
> > simply won't compile - any hint to fix it will be appreciated :)
>
> I would be tempted to agree with you, except that it works when built
> against libgc5.
My comments are interespersed below...
> --- Yann Dirson
> reassign 117513 g++-2.95
> thanks
>
> On Mon, Oct 29, 2001 at 02:01:55AM -0800, [EMAIL PROTECTED] wrote:
> > The version of openc++ in unstable will segfault.
>
> Yep.
> :(
>
> This happens in driver2.cc::RunSoCompiler(), which:
>
> 1.
Processing commands for [EMAIL PROTECTED]:
> reassign 117513 g++-2.95
Bug#117513: openc++: segfault or "Error 139" compiling anything, even empty file
Bug reassigned from package `openc++' to `g++-2.95'.
> thanks
Stopping processing here.
Please contact me if you need
5 matches
Mail list logo
