On 24 May 2010 16:44, Kris Maglione wrote:
> On Mon, 24 May 2010 19:16:52 +0400
> anonymous wrote:
>
>> On Mon, May 24, 2010 at 07:51:48AM -0400, Kris Maglione wrote:
>> > On Mon, 24 May 2010 10:02:47 +0200
>> > Premysl Hruby wrote:
>> > What version of sic are you using? The current version doe
On Mon, 24 May 2010 19:16:52 +0400
anonymous wrote:
> On Mon, May 24, 2010 at 07:51:48AM -0400, Kris Maglione wrote:
> > On Mon, 24 May 2010 10:02:47 +0200
> > Premysl Hruby wrote:
> > What version of sic are you using? The current version doesn't have
> > that code anymore.
>
> Looks like 1.0.
On Mon, May 24, 2010 at 07:51:48AM -0400, Kris Maglione wrote:
> On Mon, 24 May 2010 10:02:47 +0200
> Premysl Hruby wrote:
> What version of sic are you using? The current version doesn't have
> that code anymore.
Looks like 1.0.
On Mon, 24 May 2010 10:02:47 +0200
Premysl Hruby wrote:
> Hi,
>
> in sic, if you use cmd ":m something" it will use null pointer as %s
> in printf (in function privmsg), which is obviously bad idea
> (segfault or, as in case of glibc it send unnecessary string "(null)".
I haven't come across a
This bug is not present in tip anymore; feel free to upgrade your local sic
sources ;-)
Regards,
Claudio M. Alessi
Hi,
in sic, if you use cmd ":m something" it will use null pointer as %s in
printf (in function privmsg), which is obviously bad idea (segfault or,
as in case of glibc it send unnecessary string "(null)".
For fix, see patch:
diff -r 503b48b13a77 sic.c
--- a/sic.c Tue Jul 29 19:22:08 2008 +01
