------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=790 --- Comment #2 from Ling Meng <[email protected]> 2008-12-11 22:47:17 --- From Coverity Prevent documentation: " The STACK_USE checker finds many instances of overall stack use exceeding a configured maximum (default 32768 bytes), or of a single stack use exceeding a configured maximum (default 1024 bytes). ... To enable this checker, use the analysis option --enable STACK_USE. ... stack_use_local_overflow — A single local variable exceeded the configured maximum stack size (default 1024 bytes). " -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Nuno Lopes Sent: Thursday, December 11, 2008 2:05 PM To: Meng.Ling Subject: [Bug 790] Stack Use ------- You are receiving this mail because: ------- You reported the bug. http://bugs.exim.org/show_bug.cgi?id=790 Nuno Lopes <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Nuno Lopes <[email protected]> 2008-12-11 22:05:03 --- I've grep'ed through the C99 specification and I couldn't find any reference to that 1024 bytes limit. Moreover, I also have access to a coverity scan (PHP) and we don't have report about PCRE at the moment. So, don't you have some custom checkers in place that are triggering those warnings? Could you please point me to a document that specifies that arbitrary limitation for each local variable? -- Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email -- Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email -- ## List details at http://lists.exim.org/mailman/listinfo/pcre-dev
