> /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5/include/g++-v3/iostream:1331:
> internal compiler error: Segmentation
>fault
Ah!!! mine did that too and I'm sure it's not broken... first I
thought it was a hardware error (thigs like this are usually software
errors but I did not wanted to upgra
On Thursday 13 January 2005 10:04 am, "Dave Nebinger" <[EMAIL PROTECTED]>
wrote:
> > Most segfaults are hardware related and rarely exactly reproducible.
>
> Hah, some programmer fed you a line of crap and you chowed down on it
> ;-)
I'm a programmer too. In *my* code a seg. fault means I screwe
> Most segfaults are hardware related and rarely exactly reproducible.
Hah, some programmer fed you a line of crap and you chowed down on it ;-)
As a long-time unix programmer, I can assure you that 99.99% of segfaults
are code related, not hardware related. Segmentation faults are the result
of
On Thursday 13 January 2005 09:20 am, Radu Filip <[EMAIL PROTECTED]> wrote:
> hi, I never managed to compile openh232 (required for gnomemeeting). I
> tries also with 'CFLAGS="-O1" emerge' and same result.
So, it breaks on *exactly* the same file/method? Most segfaults are
hardware related and r
> [ output of emerge openh232 snipped ]
> /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5/include/g++-v3/iostream: In
> destructor
>`virtual
> H225_TransportAddress_ipAddress::~H225_TransportAddress_ipAddress()
>':
> /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5/include/g++-v3/iostream:1331:
> internal
