δΊ 2011/7/11 14:15, Kai Tietz ει: > So I looked a bit into libgomp's source code and I see that I might > have found the cause for this crash. See in team.c the function > gomp_new_team. Use here instead for 'team = gomp_malloc (size);' the > following 'team = gomp_malloc_cleared (size);'. This might be already > the cause for this crash. > Additional I see the gomp doesn't handle limited resources for > system-handles pretty well. So maybe reduce amount of threads used, > this could solve some issues here, too. Good work. What could I help you? I don't know how the problem is described? Do we need write a bugzilla report to libgomp.
-- Best Regards, PcX ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
