mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

force use of pandoc version >= 3.1.12.2

Browse Source 
The `bin/pandoc-wrapper.sh` tool will verify that the ssytem
has a recent enough version of `pandoc(1)`.

We explain why we insist on `pandoc(1)`. version >= 3.1.12.2
in comments where the $PANDOC_MIN_VERSION is set.

Added `--wrap=preserve` as a default argument to `pandoc(1)`.
While this change will impact every HTML file generated,
we believe this will improve the ability of someone to look
at the generated HTML and correlate with the original markdown.

Changed `bin/pandoc-wrapper.sh` VERSION from "1.4.2 2024-03-17"
to "1.4.3 2024-03-18".

Performed `make www` to achieve all of the above and to generate
HTML using the new  `--wrap=preserve` `pandoc(1)` mode.
This commit is contained in:
Landon Curt Noll committed 2024-03-18 01:26:39 -07:00
1 parent 9eb7a54e9f
commit b0b212acb1
402 files changed
+37061 -55132
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

2014/skeggs/index.html
+111 -153
View File
@@ -130,8 +130,8 @@
<h2 id="author"><a name="author"></a>Author:</h2>
<ul>
<li>Name: <a href="../../authors.html#Cel_Skeggs">Cel Skeggs</a><br>
Location: <a href="../../location.html#US">US</a> - <em>United States of
America</em> (<em>United States</em>) <br><br></li>
Location: <a href="../../location.html#US">US</a> - <em>United States of America</em> (<em>United States</em>)
<br><br></li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-author.sh -->
@@ -143,20 +143,19 @@ America</em> (<em>United States</em>) <br><br></li>
<div class="sourceCode" id="cb1"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" aria-hidden="true" tabindex="-1"></a><span class="fu">make</span></span></code></pre></div>
<h2 id="to-use">To use:</h2>
<div class="sourceCode" id="cb2"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./prog</span></span></code></pre></div>
<p>HINT: Try pressing the left and right arrow keys as needed. Also try
pressing space/enter to select options. Pressing Q or Escape may end the
fun before you are ready. :-)</p>
<p>HINT: Try pressing the left and right arrow keys as needed.
Also try pressing space/enter to select options.
Pressing Q or Escape may end the fun before you are ready. :-)</p>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>When the code looks like lemons, it is probably because the
LEMONPEOPLE, or at least the LEMONLORD was involved. :-)</p>
<p>Look at some of the C pre-processor macros in the source code. Ask
yourself why C source is being passed as arguments to some of those
macros.</p>
<p>Now you may observe, while it is running, that some C source code is
being written to a file and then compiled. And yet that compiled code is
somehow executed from <code>main()</code>. But how? How is
<code>main()</code> able to call code that was written and compiled just
in time for execution?</p>
<p>When the code looks like lemons, it is probably because the LEMONPEOPLE,
or at least the LEMONLORD was involved. :-)</p>
<p>Look at some of the C pre-processor macros in the source code.
Ask yourself why C source is being passed as arguments to some
of those macros.</p>
<p>Now you may observe, while it is running, that some C source code is being
written to a file and then compiled. And yet that compiled code is somehow
executed from <code>main()</code>. But how? How is <code>main()</code> able to call code that was
written and compiled just in time for execution?</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<h3 id="table-of-contents">TABLE OF CONTENTS</h3>
<ul>
@@ -167,142 +166,117 @@ in time for execution?</p>
<li>Q&amp;A</li>
</ul>
<h3 id="backstory">BACKSTORY</h3>
<p>It was ten yours ago when THE LEMONPEOPLE invaded, juicing all in
their path.</p>
<p>Attempting to free the Earth from their tyranny, you have endured
pulpy and sour battles.</p>
<p>This has now culminated in you reaching the throne room of THE
LEMONLORD.</p>
<p>It was ten yours ago when THE LEMONPEOPLE invaded, juicing all in their path.</p>
<p>Attempting to free the Earth from their tyranny, you have endured pulpy and
sour battles.</p>
<p>This has now culminated in you reaching the throne room of THE LEMONLORD.</p>
<p>Armed with your right-facing curly brace, you charge into battle.</p>
<p>(Use left and right arrow keys and space/enter to select options.
Press Q or Escape to quit.)</p>
<p>(Use left and right arrow keys and space/enter to select options. Press Q or
Escape to quit.)</p>
<h3 id="known-compiler-warnings">KNOWN COMPILER WARNINGS</h3>
<p>Unfortunately, it became very difficult to get this entry to fit
within the size requirements. It’s currently at 2052 according to <a
href="../iocccsize.c">iocccsize</a>, and 3994 according to
<code>wc -c</code>.</p>
<p>The current size is a third to a half of the original size before
compression.</p>
<p>Unfortunately, it became very difficult to get this entry to fit within the
size requirements. It’s currently at 2052 according to
<a href="../iocccsize.c">iocccsize</a>, and 3994 according to <code>wc -c</code>.</p>
<p>The current size is a third to a half of the original size before compression.</p>
<p>Due to this, it does LOTS of things that subtly annoy compilers!</p>
<ul>
<li><ol start="10" type="1">
<li>data argument not used by format string</li>
</ol>
<p>This occurs because some of the <code>fprintf(3)</code> invocations
don’t use all their parameters. The program should still work
fine!</p></li>
<p>This occurs because some of the <code>fprintf(3)</code> invocations don’t use all their
parameters. The program should still work fine!</p></li>
<li><ol type="1">
<li>using the result of an assignment as a condition without
parentheses</li>
<li>using the result of an assignment as a condition without parentheses</li>
</ol>
<p>Somewhere, I needed to set a variable and then branch on the result.
The shortest way was to combine them. Some self-proclaimed “EXPERTS”
think this is a bad programming practice, but what do they know?
:P</p></li>
<p>Somewhere, I needed to set a variable and then branch on the result. The
shortest way was to combine them. Some self-proclaimed “EXPERTS” think this
is a bad programming practice, but what do they know? :P</p></li>
<li><ol type="1">
<li>implicit declaration of function ‘time’ is invalid in C99</li>
</ol>
<p>An <code>#include</code> statement is expensive, and I’m
broke.</p></li>
<p>An <code>#include</code> statement is expensive, and I’m broke.</p></li>
<li><ol type="1">
<li>control may reach end of non-void function</li>
</ol>
<p>Turns out that sometimes, a <code>return</code> statement is too
much. This will never actually occur, but some C compilers think they
know more about my program than I do! :P</p></li>
<li><p>(?) Under some systems, <code>-fPIC</code> is irrelevant for
shared libraries. If so, you should remove it from the
Makefile.</p></li>
<p>Turns out that sometimes, a <code>return</code> statement is too much. This will never
actually occur, but some C compilers think they know more about my program
than I do! :P</p></li>
<li><p>(?) Under some systems, <code>-fPIC</code> is irrelevant for shared libraries. If so,
you should remove it from the Makefile.</p></li>
</ul>
<h2
id="obfuscation-what-obfuscation-this-is-a-perfectly-normal-c-program">OBFUSCATION?
WHAT OBFUSCATION? THIS IS A PERFECTLY NORMAL C PROGRAM!</h2>
<h2 id="obfuscation-what-obfuscation-this-is-a-perfectly-normal-c-program">OBFUSCATION? WHAT OBFUSCATION? THIS IS A PERFECTLY NORMAL C PROGRAM!</h2>
<h1 id="the-cool-part">THE COOL PART</h1>
<p>Take a close look at how it works. Notice that it’s passing C code to
certain macros…</p>
<p>Guess what? It’s a very simple kind of JIT compiler, though not used
as deeply as would be cool.</p>
<p>Essentially, it generates C code at runtime, dumps it to a file, and
then runs a C compiler on that file, telling the C compiler to generate
a shared library. Then it loads the shared library with
<code>dlopen(3)</code>, and…</p>
<p>Take a close look at how it works. Notice that it’s passing C code to certain
macros…</p>
<p>Guess what? It’s a very simple kind of JIT compiler, though not used as deeply
as would be cool.</p>
<p>Essentially, it generates C code at runtime, dumps it to a file, and then runs
a C compiler on that file, telling the C compiler to generate a shared library.
Then it loads the shared library with <code>dlopen(3)</code>, and…</p>
<p>Ignores the result?</p>
<p>That can’t be right.</p>
<p>Well, it is. Instead of using <code>dlsym(3)</code> like a normal
programmer, I mark one of the generated functions with
<code>__attribute__((constructor))</code>. This means that it gets
called immediately on load, so it can make its functions available.</p>
<p>But wait - how can it link into the main program, either? It has no
way to reference anything in the main executable!</p>
<p>But it does: I’m injecting certain addresses into the generated code,
which it then casts to pointers and accesses! It uses this to make
certain functions available to the main program, so the main program’s
generated code will then enter itself where it’s needed.</p>
<p>Well, it is. Instead of using <code>dlsym(3)</code> like a normal programmer, I mark one of the
generated functions with <code>__attribute__((constructor))</code>. This means that it
gets called immediately on load, so it can make its functions available.</p>
<p>But wait - how can it link into the main program, either? It has no way to
reference anything in the main executable!</p>
<p>But it does: I’m injecting certain addresses into the generated code, which it
then casts to pointers and accesses! It uses this to make certain functions
available to the main program, so the main program’s generated code will then
enter itself where it’s needed.</p>
<h1 id="the-not-so-cool-part">THE NOT-SO-COOL PART</h1>
<p>There are also lots of <code>#defines</code>.</p>
<p>No, these are not obfuscation. These are compression.</p>
<p>There is a little bit of obfuscation gained from using the
stringification operator. (I can never remember what it’s actually
called, but it’s the <code>#</code> operator in a preprocessor macro) -
this allows me to pass C code in arguments to the macros, meaning that
it gets interpreted as C code instead of a string by the <a
href="../iocccsize.c">iocccsize</a> tool, so it gets counted as smaller!
:D</p>
<p>There is a little bit of obfuscation gained from using the stringification
operator. (I can never remember what it’s actually called, but it’s the <code>#</code>
operator in a preprocessor macro) - this allows me to pass C code in arguments
to the macros, meaning that it gets interpreted as C code instead of a string
by the <a href="../iocccsize.c">iocccsize</a> tool, so it gets counted as smaller! :D</p>
<h1 id="a-slightly-cool-part">A SLIGHTLY COOL PART</h1>
<p>As part of the JIT compiling, the program hides the fact that it
needs ncurses: it just links ncurses with one of the generated shared
libraries, and then can access the contents of the ncurses library!</p>
<p>As part of the JIT compiling, the program hides the fact that it needs ncurses:
it just links ncurses with one of the generated shared libraries, and then can
access the contents of the ncurses library!</p>
<h1 id="wait-what">WAIT WHAT</h1>
<p>Also, note where functions start and end…</p>
<p>I’ve messed with the syntax so that it’s not actually formatted
properly. It almost looks like it is, but it isn’t.</p>
<p>This isn’t significant obfuscation as long as you run it through a C
source code beautifier.</p>
<p>I’ve messed with the syntax so that it’s not actually formatted properly. It
almost looks like it is, but it isn’t.</p>
<p>This isn’t significant obfuscation as long as you run it through a C source
code beautifier.</p>
<p>But wait… if you aren’t careful, running it through a C source code
beautifier won’t work. Remember how I’m interlacing generated C code
with actual C code? Note that this WRECKS some beautifiers. I hope you
have a good one!</p>
<p>(There’s an obvious way around this but I’m not going to spell it out
for you. That’d be too easy!)</p>
beautifier won’t work. Remember how I’m interlacing generated C code with
actual C code? Note that this WRECKS some beautifiers. I hope you have a good
one!</p>
<p>(There’s an obvious way around this but I’m not going to spell it out for you.
That’d be too easy!)</p>
<h3 id="miscellaneous-stuff">MISCELLANEOUS STUFF</h3>
<p>Do note that there are some other miscellaneous obfuscations, but
they should be easy to understand once you figure out the ones
above.</p>
<p>Do note that there are some other miscellaneous obfuscations, but they should
be easy to understand once you figure out the ones above.</p>
<h3 id="troubleshooting-guide">TROUBLESHOOTING GUIDE</h3>
<p>This program is a very easy program to cause to fail!</p>
<p>Some things to check</p>
<ul>
<li><p>On line 16, where it says <code>%cinclude "prog.c"</code>, is
<code>prog.c</code> the name of the original source code file?</p></li>
<li><p>On line 16, where it says <code>%cinclude "prog.c"</code>, is <code>prog.c</code> the name of the
original source code file?</p></li>
<li><p>Do you have ncurses installed?</p></li>
<li><p>Does your system have <code>ncurses.h</code> (like a nice system)
or <code>ncurses/ncurses.h</code> (like a rude system) ?</p>
<p>If it’s the latter (or some other path), you’ll need to update line
97.</p>
<li><p>Does your system have <code>ncurses.h</code> (like a nice system) or
<code>ncurses/ncurses.h</code> (like a rude system) ?</p>
<p>If it’s the latter (or some other path), you’ll need to update line 97.</p>
<p>(I had to do this under Cygwin.)</p></li>
<li><p>Does your system need <code>-fPIC</code> (or other arcane
invocations) to compile a shared library? If so, make sure that you
include it in the <code>-DCC</code> argument in the build
script.</p></li>
<li><p>Does your system have a vague dislike for <code>-fPIC</code>?
(Like Cygwin.) You might need to remove it from the build
script.</p></li>
<li><p>Does your system support
<code>__attribute__((constructor))</code>? It needs to.</p></li>
<li><p>Check the file <code>err</code>. Maybe it will help you figure
out why a runtime- generated program failed. The failing program should
be found in <code>t.c</code>.</p></li>
<li><p>Can’t run a beautifier on the source code? I’m not going to help
you there.</p></li>
<li><p>Does your system need <code>-fPIC</code> (or other arcane invocations) to compile a
shared library? If so, make sure that you include it in the <code>-DCC</code> argument in
the build script.</p></li>
<li><p>Does your system have a vague dislike for <code>-fPIC</code>? (Like Cygwin.) You might
need to remove it from the build script.</p></li>
<li><p>Does your system support <code>__attribute__((constructor))</code>? It needs to.</p></li>
<li><p>Check the file <code>err</code>. Maybe it will help you figure out why a runtime-
generated program failed. The failing program should be found in <code>t.c</code>.</p></li>
<li><p>Can’t run a beautifier on the source code? I’m not going to help you there.</p></li>
</ul>
<p>I’ve tested it on the following platforms, in case you need to try it
on one:</p>
<p>I’ve tested it on the following platforms, in case you need to try it on one:</p>
<ul>
<li>64-bit Windows 7 32-bit Cygwin with gcc 4.8.2 and standards c89,
c90, c99, and c11. Note that the program ran as 32-bit due to the
version of cygwin.</li>
<li>64-bit Arch Linux with gcc 4.9.1 and standards c89, c90, c99,
c11.</li>
<li>64-bit Windows 7 32-bit Cygwin with gcc 4.8.2 and standards c89, c90, c99,
and c11. Note that the program ran as 32-bit due to the version of cygwin.</li>
<li>64-bit Arch Linux with gcc 4.9.1 and standards c89, c90, c99, c11.</li>
<li>64-bit Arch Linux with clang 3.5.0 and standards c89 and c11.</li>
</ul>
<p>I ran out of time to test it on more systems.</p>
@@ -311,60 +285,44 @@ c11.</li>
<li><p>Who am I?</p>
<p>Yes.</p></li>
<li><p>Why doesn’t your program require a pet fish license?</p>
<p>THE LEMONLORD’s pet LEMONFISH was not rendered in the game, and so
does not require a pet fish license.</p></li>
<p>THE LEMONLORD’s pet LEMONFISH was not rendered in the game, and so does not
require a pet fish license.</p></li>
<li><p>Was this inspired by anything?</p>
<p>Yes, this was inspired by a minigame from an open-source codebase of
Space Station 13. I didn’t, however, look at the minigame at all during
the development of this entry.</p></li>
<li><p>What’s the length of this README file according to the <a
href="../iocccsize.c">iocccsize</a> tool?</p>
<p>$ ./iocccsize -i &lt; README.md 6057</p></li>
<p>Yes, this was inspired by a minigame from an open-source codebase of Space
Station 13. I didn’t, however, look at the minigame at all during the
development of this entry.</p></li>
<li><p>What’s the length of this README file according to the
<a href="../iocccsize.c">iocccsize</a> tool?</p>
<p>$ ./iocccsize -i &lt; README.md
6057</p></li>
</ul>
<h2 id="copyright-and-cc-by-sa-4.0-license">Copyright and CC BY-SA 4.0
License:</h2>
<p>This file is Copyright (c) 2023 by Landon Curt Noll. All Rights
Reserved. You are free to share and adapt this file under the terms of
this license:</p>
<h2 id="copyright-and-cc-by-sa-4.0-license">Copyright and CC BY-SA 4.0 License:</h2>
<p>This file is Copyright (c) 2023 by Landon Curt Noll. All Rights Reserved.
You are free to share and adapt this file under the terms of this license:</p>
<pre><code>Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)</code></pre>
<p>For more information, see:
https://creativecommons.org/licenses/by-sa/4.0/</p>
<p>For more information, see: https://creativecommons.org/licenses/by-sa/4.0/</p>
<!-- END: this line ends content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
<!-- START: this line starts content for HTML phase 22 by: bin/output-index-inventory.sh via bin/md2html.sh -->
<!-- START: this line starts content generated by: bin/output-index-inventory.sh -->
<h1 id="inventory-for-2014skeggs"><a name="inventory"></a>Inventory for
2014/skeggs</h1>
<h1 id="inventory-for-2014skeggs"><a name="inventory"></a>Inventory for 2014/skeggs</h1>
<p><a href="#top">Jump to top</a></p>
<h2 id="primary-files">Primary files</h2>
<ul>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2014/skeggs/prog.c">prog.c</a>
- entry source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2014/skeggs/Makefile">Makefile</a>
- entry Makefile</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2014/skeggs/prog.orig.c">prog.orig.c</a>
- original source</li>
<li><a href="2014_skeggs.tar.bz2">2014_skeggs.tar.bz2</a> - download
entry source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2014/skeggs/prog.c">prog.c</a> - entry source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2014/skeggs/Makefile">Makefile</a> - entry Makefile</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2014/skeggs/prog.orig.c">prog.orig.c</a> - original source</li>
<li><a href="2014_skeggs.tar.bz2">2014_skeggs.tar.bz2</a> - download entry source</li>
</ul>
<h2 id="secondary-files">Secondary files</h2>
<ul>
<li><a href="index.html">index.html</a> - entry home page</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2014/skeggs/.entry.json">.entry.json</a>
- description of entry in JSON</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2014/skeggs/.gitignore">.gitignore</a>
- list of files that should not be committed under git</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2014/skeggs/.entry.json">.entry.json</a> - description of entry in JSON</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2014/skeggs/.gitignore">.gitignore</a> - list of files that should not be committed under git</li>
<li><a href=".path">.path</a> - directory path from top directory</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2014/skeggs/README.md">README.md</a>
- markdown source for index.html</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2014/skeggs/README.md">README.md</a> - markdown source for index.html</li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-inventory.sh -->