On Thu, Apr 18, 2013 at 1:50 AM, Ben Hutchings wrote:
> It does depend on how large a job you're giving to doxygen. It
> presumably needs to hold a lot of information about the source code it
> scans in memory, so that it can generate cross-references.
>
I think you are right, particularly consi
Hi Ben,
I did the following test this weekend:
-Power off the machine
-Remove the USB dongle (taint?)
-Power up the machine
-Log in and run doxygen as before
It still crashes. This is, seemingly, the related message:
Apr 14 06:37:59 Debianosaur kernel: [137278.487402] doxygen[2535]:
segfault at 0
On Fri, Apr 5, 2013 at 4:55 PM, Ben Hutchings wrote:
> Control: reopen -1
> Control: retitle -1 Kernel soft-lockup when running doxygen
>
> On Fri, Apr 05, 2013 at 03:16:06PM -0400, Olivier Diotte wrote:
>> Hi Ben,
>>
>> I am pretty sure that running doxygen
ou configure it to do so (softlockup_panic
> kernel parameter).
>
> Ben.
>
> --
> Ben Hutchings
> We get into the habit of living before acquiring the habit of thinking.
> - Albert Camus
>
> -- For
Package: linux-2.6
Version: 2.6.32-48squeeze1
Severity: important
Tags: squeeze
Here is an example of what appears in kern.log when the system crashes:
6433 Apr 4 00:35:13 Debianosaur kernel: [57842.080076] INFO: task
doxygen:22882 blocked for more than 120 seconds.
6434 Apr 4 00:35:13 Debianos
5 matches
Mail list logo
