unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Aidan Gauland <aidalgol@no8wireless.co.nz>
To: Andy Wingo <wingo@pobox.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 13018@debbugs.gnu.org
Subject: bug#13018: fport_fill_input should handle EINTR
Date: Fri, 29 Mar 2013 20:35:53 +1300	[thread overview]
Message-ID: <87mwtmmzdy.fsf@dimension8.tehua.net> (raw)
In-Reply-To: <87sj3zh6cy.fsf@pobox.com> (Andy Wingo's message of "Wed, 13 Mar 2013 12:44:13 +0100")

> Aidan, do you have a test case?

I haven't been able to reproduce this with a minimal example, but I can
consistently reproduce it with my IRC bot
<https://github.com/aidalgol/cunning-bot>.

Replace the last two lines (lines 22 and 23) of run-cbot.scm with...

(define bot (make-bot "Cunning_Bot" "Cunning_Bot" "Cunning Bot" "chat.freenode.net" 6667))
(sigaction SIGINT
  (lambda ()
    (disconnect-bot bot)))
(start-bot bot '("#cunningbot"))

...run it (run-cbot.scm), and after it says

Setting up IRC connection...done.
Joining channels...done.

type ^C

I get this backtrace:

^CBacktrace:
In ice-9/boot-9.scm:
 157: 12 [catch #t #<catch-closure 9a1020> ...]
In unknown file:
   ?: 11 [apply-smob/1 #<catch-closure 9a1020>]
In ice-9/boot-9.scm:
  63: 10 [call-with-prompt prompt0 ...]
In ice-9/eval.scm:
 421: 9 [eval # #]
In ice-9/boot-9.scm:
2131: 8 [save-module-excursion #<procedure 9a01c0 at ice-9/boot-9.scm:3711:3 ()>]
3718: 7 [#<procedure 9a01c0 at ice-9/boot-9.scm:3711:3 ()>]
In unknown file:
   ?: 6 [load-compiled/vm "/home/aidan/.cache/guile/ccache/2.0-LE-8-2.0/home/aidan/src/cunning-bot/run-cbot.scm.go"]
In /home/aidan/src/cunning-bot/bot.scm:
 260: 5 [start-bot # #]
 115: 4 [read-line-irc #]
In ice-9/rdelim.scm:
 129: 3 [read-line #<input-output: socket 11> trim]
In unknown file:
   ?: 2 [%read-line #<input-output: socket 11>]
In ice-9/boot-9.scm:
 184: 1 [throw system-error "fport_fill_input" "~A" ("Interrupted system call") (4)]
In /home/aidan/src/cunning-bot/run-cbot.scm:
  24: 0 [#<procedure 12007a0 at /home/aidan/src/cunning-bot/run-cbot.scm:24:2 ()> 2]

/home/aidan/src/cunning-bot/run-cbot.scm:24:2: In procedure #<procedure 12007a0 at /home/aidan/src/cunning-bot/run-cbot.scm:24:2 ()>:
/home/aidan/src/cunning-bot/run-cbot.scm:24:2: Wrong number of arguments to #<procedure 12007a0 at /home/aidan/src/cunning-bot/run-cbot.scm:24:2 ()>

Could this be caused by a bug in spells?

I wish I could give a simpler test case. :(

Regards,
Aidan Gauland

(Sorry I forgot to group reply the first time.)





  reply	other threads:[~2013-03-29  7:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28  8:19 bug#13018: fport_fill_input should handle EINTR Aidan Gauland
2012-11-29 20:19 ` Ludovic Courtès
2013-03-13 11:44   ` Andy Wingo
2013-03-29  7:35     ` Aidan Gauland [this message]
2013-07-03 19:14     ` Mark H Weaver
2013-08-08 21:39       ` Mark H Weaver
2013-03-05 17:57 ` Andy Wingo

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mwtmmzdy.fsf@dimension8.tehua.net \
    --to=aidalgol@no8wireless.co.nz \
    --cc=13018@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=wingo@pobox.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).