From: Hrvoje Niksic <hniksic@srce.hr>
Cc: ding@gnus.org
Subject: The horrible bug
Date: 04 Apr 1998 03:42:28 +0200 [thread overview]
Message-ID: <kigsonubbwb.fsf@jagor.srce.hr> (raw)
At least I've found how to work around the bug: Turn off the sparse
threads. This is probably also the reason why noone noticed it -- it
shows up only with sparse threads turned on.
--
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
main(){printf(&unix["\021%six\012\0"],(unix)["have"]+"fun"-0x60);}
next reply other threads:[~1998-04-04 1:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-04 1:42 Hrvoje Niksic [this message]
1998-04-04 5:13 ` Eze Ogwuma
1998-04-04 8:16 ` Hallvard B Furuseth
1998-04-04 14:14 ` Hrvoje Niksic
1998-04-04 20:59 ` Kim-Minh Kaplan
1998-04-04 20:19 ` Hrvoje Niksic
1998-04-04 22:22 ` Eze Ogwuma
1998-04-05 21:57 ` Kim-Minh Kaplan
1998-04-07 20:26 ` Eze Ogwuma
1998-04-14 17:44 ` Kim-Minh Kaplan
1998-04-14 19:01 ` Eze Ogwuma
1998-04-16 2:06 ` Eze Ogwuma
1998-04-08 10:11 ` Thomas Hungenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=kigsonubbwb.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).