Hi Chris, Yes, my bad, should've attach preprocessed source at first, Now it's wierd if I invoke cc to compile preprocessed source file, the object is built without a problem, whereas Makefile (gmake) is used, cc will run abnormally long and consumes about 12M memory + 50% CPU of a dual core 2.2GHz Opteron.
For the reference, preprocessed source is attached. but as I said, cc built it ok. Cheers, Ivan. > For future reference: > The point of doing "cc -E" is so that when you post > the source code, anyone can > try compiling for themselves. If you don't do that, > then the missing headers prevent > anyone from reproducing it without downloading the > same version of wireshark. > > --chris > > > Ivan Wang wrote: > > Hi all, > > > > I was in the middle of building wireshark 0.99.7 > (formerly known as ethereal) and ran into this > problem. > > > > Sun Studio 11 cc hangs (I've once left it > overnight, and still the no output, the prstat below > is just another attempt I tried) when compiling a > not-too-complicated C source file, > > according to prstat, cc (actually acomp) can grow > to 1xM in RSS like: > > > > PID USERNAME SIZE RSS STATE PRI NICE > TIME CPU PROCESS/NLWP > 133 wangyf 21M 18M cpu1 10 0 0:35:15 > 50% acomp/1 > > The file itself is nothing too complex, attached for > reference. > I've tried "cc -E" to see if there is any obvious > error, but cc -E gives preprocessed result without > any problem. > > And gcc also compiles the file without warning. > Is it some unknown bug in Sun Studio 11? > > My cc is patched to 121016-07 and 120759-15 > > Cheers, > Ivan. > -- > This message posted from opensolaris.org > > > ----------------------------------------------------- > ------------------ > > > > _______________________________________________ > > tools-compilers mailing list > > tools-compilers at opensolaris.org > _______________________________________________ > tools-compilers mailing list > tools-compilers at opensolaris.org Hi -- This message posted from opensolaris.org
