Re: Crashing when using make with option -j.

2010-03-18 Thread tom honermann
On 3/18/2010 2:22 PM, Thiago C. Santini wrote: Yeah, that was my first thought when using -j, 8 processors each one with hyper-threading should be optimized with 16 jobs but when testing it I got better results with 32 jobs and that was working just fine till last week, so I just sticked to it

Re: Crashing when using make with option -j.

2010-03-18 Thread Thiago C. Santini
On Thu, Mar 18, 2010 at 5:41 PM, Paul Smith wrote: > On Thu, 2010-03-18 at 14:57 -0300, Thiago C. Santini wrote: > > We have a computer in our lab we use to run simulations and sometimes > > compiling. It's been working just fine for over 6 months now but > > during the last week we had it's firs

Re: Crashing when using make with option -j.

2010-03-18 Thread Paul Smith
On Thu, 2010-03-18 at 14:57 -0300, Thiago C. Santini wrote: > We have a computer in our lab we use to run simulations and sometimes > compiling. It's been working just fine for over 6 months now but > during the last week we had it's first 3 crashes(only fixable by hard > restarting the machine). I

Crashing when using make with option -j.

2010-03-18 Thread Thiago C. Santini
We have a computer in our lab we use to run simulations and sometimes compiling. It's been working just fine for over 6 months now but during the last week we had it's first 3 crashes(only fixable by hard restarting the machine). I'm not a very experienced linux user so all I tried to do to find ou

[bug #29253] Memory corruption error when backslash line continuation used in function call

2010-03-18 Thread anonymous
Additional Item Attachment, bug #29253 (project make): File name: make-fix.patch Size:0 KB ___ Reply to this item at: ___ Message sent

[bug #29253] Memory corruption error when backslash line continuation used in function call

2010-03-18 Thread anonymous
URL: Summary: Memory corruption error when backslash line continuation used in function call Project: make Submitted by: None Submitted on: Thu 18 Mar 2010 08:26:54 AM UTC Severity: 3