xchat2 - perl plugin makes xchat2 core dump

Randy Pratt rpratt1950 at earthlink.net
Mon Jun 14 09:29:53 PDT 2004


On Thu, 29 Apr 2004 17:05:03 -0500
Jeremy Messenger <mezz7 at cox.net> wrote:

> On Thu, 29 Apr 2004 17:44:53 -0400, Randy Pratt <rpratt1950 at earthlink.net> 
> wrote:
> 
> > On Thu, 29 Apr 2004 14:14:13 -0500
> > Jeremy Messenger <mezz7 at cox.net> wrote:
> >
> >> On Thu, 29 Apr 2004 14:12:42 -0400, Randy Pratt 
> >> <rpratt1950 at earthlink.net>
> >> wrote:
> >>
> >> > On Thu, 29 Apr 2004 13:13:18 -0400
> >> > Joe Marcus Clarke <marcus at marcuscom.com> wrote:
> >> >
> >> > <snip other discussion>
> >> >
> >> > I renamed my ~/.xchat2 directory and tried a clean startup.  And I
> >> > can load the perl.so module without crashing xchat2.  Note that the
> >> > warning about not being able to preload is still present, but it
> >> > does not crash:
> >> >
> >> >    AutoLoad failed for:
> >> >    /usr/X11R6/lib/xchat/plugins/perl.so
> >> >
> >> >    No xchat_plugin_init symbol; is this really an xchat plugin?
> >>
> >> No error here..
> >
> > I should have been clearer on that.  It shows up in the server window
> > of xchat2 and not an xterm.
> >
> > Did the perl.so really autoload for you or did you have to load it
> > manually?
> 
> It did autoload the perl.so for me, but I don't remember how to get script 
> autoload thought.
> 
> In xchat (in the first line):
> ======================================
>   Perl interface loaded
> ======================================
> 
> In the 'Windows -> Plugins and Scripts' menu shows that perl.so loaded by 
> itself. Perhaps, try a new ~/.xchat2 again to see if it helps?

A little update on the autoloading of the perl interface in xchat2:

I received a private email today that suggested that I try
unchecking the option "No server list on startup" and the perl
interface would autoload.

It didn't quite work out that way for me, but if I *check* the
option "No server list on startup".  I get the "Perl interface
loaded" when xchat2 starts up.

FWIW, I copied the .xchat2 directory to .xchat2-works and
fiddled with the "No server list on startup" setting so that
it didn't autoload perl, then compared the two directories:

  $ diff -ruN .xchat2 .xchat2-works
  diff -ruN .xchat2/xchat.conf .xchat2-works/xchat.conf
  --- .xchat2/xchat.conf  Mon Jun 14 12:14:44 2004
  +++ .xchat2-works/xchat.conf    Mon Jun 14 12:13:38 2004
  @@ -50,7 +50,7 @@
   gui_mode_buttons = 0
   gui_slist_edit = 1
   gui_slist_select = 70
  -gui_slist_skip = 0
  +gui_slist_skip = 1
   gui_throttlemeter = 3
   gui_topicbar = 1
   gui_ulist_buttons = 1

I've not dug into it further but it looks like that option is
triggering some bug.  At least its a point that may be able to
duplicate the behavior that I was seeing.

OS and ports are up to date:

FreeBSD kt.weeble.com 4.10-STABLE FreeBSD 4.10-STABLE #0:
Sat Jun  5 15:39:24 EDT 2004
rpratt at kt.weeble.com:/usr/obj/usr/src/sys/CUSTOM  i386

xchat2-2.0.9        An X11 IRC client using the GTK+ 2 toolkit

This is perl, v5.8.4 built for i386-freebsd-64int

Best regards,

Randy

-- 


More information about the freebsd-gnome mailing list