Timeline for Generate the longest error message in C++
Current License: CC BY-SA 2.5
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 31, 2018 at 5:05 | comment | added | David Stone |
A pattern like this will get you further: #define A(s) s##s##s##s #define B(s) A(s) #define C(s) B(B(B(s))) #define D(s) C(C(C(s))) D(foo) . This gets me an error message about as long with much less code, and grows much faster with increasing the pattern in any dimension, since we are essentially implementing the Ackermann function.
|
|
Dec 17, 2013 at 4:39 | comment | added | Demi | Not really a big deal - gcc tries to allocate too much space on the stack. Using ulimit -s unlimited prevents the crash. Adding another seven layers of macros I can get it to die with virtual memory exhausted. | |
May 5, 2011 at 6:42 | comment | added | the_drow | @muntoo: How come? An ICE is never a good idea. | |
May 5, 2011 at 4:50 | comment | added | Mateen Ulhaq | @the_drow It's a feature. | |
Apr 15, 2011 at 12:09 | comment | added | the_drow | @JoeyAdams: Please report this as a bug than | |
Apr 5, 2011 at 17:12 | comment | added | Joey Adams | gcc 4.4.5 segfaults. Win! | |
Apr 5, 2011 at 16:18 | comment | added | Keith Randall | @Elazar: OK, fixed. | |
Apr 5, 2011 at 16:17 | history | edited | Keith Randall | CC BY-SA 2.5 |
Make the whole error on a single line.
|
Apr 5, 2011 at 7:47 | comment | added | Elazar Leibovich | Read the instructions! You should generate a single long error, not many short errors. | |
Apr 5, 2011 at 3:47 | history | answered | Keith Randall | CC BY-SA 2.5 |