Re: system() call causes gcc-x64 profiling to crash

[Vincent Diepeveen <diep at xs4all dot nl>]

Thanks Andrew,

We figured out the problem in the meantime: setting a signal at start  
of program causes that profiler gives error on system() function.



On Dec 20, 2007, at 11:28 AM, Andrew Haley wrote:

> Vincent Diepeveen writes:
> > Good morning,
> >
> > When we try to profile (-pg and with optimizations turned on)
> > at SUSE x64 gcc 4.2.2, then the software gets hung at the
> > point of calling the function system() in c++ code.
> >
> > We are using both intel as well as amd hardware it gets hung at  
> > them all.
> >
> > What is the best way for us to get around this and proceed?
>
> Produce a simple test case and then we'll be able to talk about it.
> As it stands we don't know if this is a kernel problem, libc, or gcc.
> Maybe you're just using it wrong.
>
> Andrew.
>
> --
> Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor,  
> Berkshire, SL4 1TE, UK
> Registered in England and Wales No. 3798903