
Greetings, now I have a working plugins package, I can refocus on my lambdabot problem. Let me recap: In Lib/Parser.hs, as_name &c are defined #if __GLASGOW_HASKELL__ > 606, however ghc-6.6.1 defines that as 606, so to go through the build, I had to change the '>' to '>='. Is that a bad idea? (otherwise that should be changed in Parser.ly/.hs) Next, in scripts/ShowQ.hs, there is defined an instance (Arbitrary a) => Arbitrary (Maybe a), but such an instance already is defined in Test.QuickCheck, so I commented the one in ShowQ out (after the build died there once). That probably should be fixed in the darcs repo. As anything of the above stupid/dangerous? Okay, so building succeeds without complaints, but then $ ./lambdabot Initialising plugins ................Speicherzugriffsfehler Changing BotPP so that it created a persisting copy of its output, I found out what modulesInfo does, then, letting ircInstallModule produce debugging output, I located the evildoers. lambdabot segfaulted when installing Fact Haddock Quote Source Todo Where What's special about them? I.e., why did they cause a segfault and the others not? And, how could I build a lambdabot _with_ them (though I'm not sure, I'll actually want them, but I might). Without these, I now have an apparently working lambdabot, well, not properly working. First time I started it, all seemed well, but from then on: $ ./lambdabot Initialising plugins ..................................sending message to bogus server: IrcMessage {msgServer = "freenode", msgLBName = "urk!<outputmessage>", msgPrefix = "", msgCommand = "NAMES", msgParams = [""]} ............... done. Main: caught (and ignoring) IRCRaised Data.ByteString.index: index too large: 0, length = 0 lambdabot> > 3+7 Main: caught (and ignoring) IRCRaised Data.ByteString.index: index too large: 0, length = 0 10 lambdabot> The bogus message thing also appeared the first time, I hope this is meant to be so. But what about the ByteString.index exception? Where might that come from? How to get rid of it? Finally, is there a tutorial/manual for using lambdabot? Thanks for any help, Daniel

Perhaps in here we should start using
\x -> (unlines . (dropWhile (/= x)) . lines)
Instead :)
Dave,
On 23/06/07, Thomas Schilling
On 22 jun 2007, at 22.17, Derek Elkins wrote:
[blah blah blah]
A less (potentially) offensive way of formulating this is:
[...]
or
-snip-
(You know, we don't want to accidentally piss of any newcomers. So just saying .. :)
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

I can partially answer my questions. Removing also Seen does away with the ByteString.index error. Must check the code to see why. Two more concrete questions a) how do I gracefully leave lambdabot? ctrl-C or killing it from another shell are the only ways out I found so far. b) what does lambdabot expect in the fptools directory? Cheers, Daniel Am Freitag, 22. Juni 2007 20:10 schrieb ich:
Greetings, lambdabot segfaulted when installing Fact Haddock Quote Source Todo Where
What's special about them? I.e., why did they cause a segfault and the others not?
And, how could I build a lambdabot _with_ them (though I'm not sure, I'll actually want them, but I might).
Without these, I now have an apparently working lambdabot, well, not properly working. First time I started it, all seemed well, but from then on: $ ./lambdabot Initialising plugins ..................................sending message to bogus server: IrcMessage {msgServer = "freenode", msgLBName = "urk!<outputmessage>", msgPrefix = "", msgCommand = "NAMES", msgParams = [""]} ............... done. Main: caught (and ignoring) IRCRaised Data.ByteString.index: index too large: 0, length = 0 lambdabot> > 3+7 Main: caught (and ignoring) IRCRaised Data.ByteString.index: index too large: 0, length = 0 10 lambdabot>
The bogus message thing also appeared the first time, I hope this is meant to be so. But what about the ByteString.index exception? Where might that come from? How to get rid of it?
Finally, is there a tutorial/manual for using lambdabot?
Thanks for any help, Daniel

On Fri, Jun 22, 2007 at 10:37:55PM +0200, Daniel Fischer wrote:
I can partially answer my questions. Removing also Seen does away with the ByteString.index error. Must check the code to see why.
Two more concrete questions a) how do I gracefully leave lambdabot? ctrl-C or killing it from another shell are the only ways out I found so far.
"quit"
b) what does lambdabot expect in the fptools directory?
Absolutely nothing. It's dead code. Stefan

Am Freitag, 22. Juni 2007 22:43 schrieb Stefan O'Rear:
On Fri, Jun 22, 2007 at 10:37:55PM +0200, Daniel Fischer wrote:
I can partially answer my questions. Removing also Seen does away with the ByteString.index error. Must check the code to see why.
Two more concrete questions a) how do I gracefully leave lambdabot? ctrl-C or killing it from another shell are the only ways out I found so far.
"quit"
Well, that's something obvious to try, of course I did: $ ./lambdabot Initialising plugins ................................................ done. lambdabot> quit Quit lambdabot> @quit Quit lambdabot> Quit Quit lambdabot> @Quit Quit lambdabot> :quit Quit lambdabot> :Quit Quit lambdabot> exit Maybe you meant: elite quit lambdabot> :exit Unknown command, try @list lambdabot> @exit Unknown command, try @list lambdabot> "quit" Quit lambdabot> "Quit" Unknown command, try @list lambdabot> So it seems my lambdabot is not only partial, but actually broken :-(
b) what does lambdabot expect in the fptools directory?
Absolutely nothing. It's dead code.
Good.
Stefan
Derek Elkins wrote:
Finally, is there a tutorial/manual for using lambdabot?
Um... #haskell...
I have no DSL and pay by the minute => not an option, unfortunately. Thanks, Daniel

On Sat, Jun 23, 2007 at 01:48:37PM +0200, Daniel Fischer wrote:
Am Freitag, 22. Juni 2007 22:43 schrieb Stefan O'Rear:
On Fri, Jun 22, 2007 at 10:37:55PM +0200, Daniel Fischer wrote:
I can partially answer my questions. Removing also Seen does away with the ByteString.index error. Must check the code to see why.
Two more concrete questions a) how do I gracefully leave lambdabot? ctrl-C or killing it from another shell are the only ways out I found so far.
"quit"
Well, that's something obvious to try, of course I did: $ ./lambdabot Initialising plugins ................................................ done. lambdabot> quit
Quit
So it seems my lambdabot is not only partial, but actually broken :-(
Oh... sorry. @quit only works on IRC connections; you would need ^D (to a 1st approximation, the unix end-of-file control character) here. (I wrote this section of code and I misremembered it badly enough to give wrong advice... *shdder*) Stefan
participants (5)
-
Daniel Fischer
-
Dave Tapley
-
Derek Elkins
-
Stefan O'Rear
-
Thomas Schilling