On Thu, Apr 18, 2013 at 1:50 AM, Ben Hutchings <[email protected]> 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 considering I was doing a doxygen run with insane options (caller graph, calling graph and what not) on kernel sources. I knew it would take a lot of memory, but I thought 2 GiB + 2 GiB swapspace was more than enough (yeah, I was a bit naive to put it lightly). In the mean time, I discovered cscope which is I like better than doxygen anyway. Well, seems like nothing has to be solved finally: doxygen probably runs out of memory and anyway I prefer cscope. The computer locks up sometimes, but that is probably due to my staging wireless driver. Thanks for your help, Olivier -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/CAM3Q4oFRNagCaYf2uCWjw-6hEUVTif=b3xqufbbzm1z68c1...@mail.gmail.com
