Date: Wed, 20 Jan 2010 10:53:36 +0100 From: Matias <matiassurdi@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: Help with core dump Message-ID: <hj6jqv$la2$1@ger.gmane.org> In-Reply-To: <hj6hp8$epk$1@ger.gmane.org> References: <hj6hp8$epk$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
El 20/01/10 10:18, Matias escribió: > Hi, > > I've installed from ports net-im/mu-conference, but whenever I try to > start it I get a core dump. > > Running it through gdb I get the following: > > > ]# gdb /usr/local/bin/mu-conference > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "amd64-marcel-freebsd"...(no debugging > symbols found)... > (gdb) run -c /usr/local/etc/muc.xml > Starting program: /usr/local/bin/mu-conference -c /usr/local/etc/muc.xml > (no debugging symbols found)...(no debugging symbols found)...(no > debugging symbols found)...(no debugging symbols found)...(no debugging > symbols found)...(no debugging symbols found)...[New LWP 100228] > (no debugging symbols found)...(no debugging symbols found)...(no > debugging symbols found)...(no debugging symbols found)...(no debugging > symbols found)...[New Thread 8015021c0 (LWP 100228)] > Jabber Component Runtime -- 0.2.4 > (c) 2003-2004 Paul Curtis > > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 8015021c0 (LWP 100228)] > 0x0000000800eaa386 in strlen () from /lib/libc.so.7 > (gdb) > > > > # uname -a > FreeBSD it05.ex.local 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 > 15:02:08 UTC 2009 > root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > > > > # cat /usr/local/etc/muc.xml > <jcr> > <!-- > This is a config file for a copy of MU-Conference, compiled against > the Jabber Component Runtime (JCR). This is the same file that I use > to connect to my development server, running jabberd2 beta2 > > In order to connect to a jabberd v1.4 server, simply change the > <name> value to muclinker, and make sure the muclinker section is in > your main jabber.xml file, as per the MU-Conference README file. > --> > > <name>conference.localhost</name> <!-- the jid of your component --> > <host>conference.localhost</host> <!-- this should be the same as above --> > <ip>localhost</ip> <!-- adress of the jabber server --> > <port>7009</port> <!-- port used to connect the service to the jabber > server --> > <secret>Vonyunya</secret> <!-- secret shared with the jabber server --> > > <spool>/var/spool/jabberd/conference.localhost</spool> <!-- directory > containing the rooms data --> > <logdir></logdir> <!-- directory containing the debug log (the file is > called mu-conference.log) --> > <pidfile>/var/run/jabberd/mu-conference.pid</pidfile> <!-- file that > will contain the PID of the process --> > > <!-- <logstderr/> --> <!-- uncomment to also send log to stderr --> > > <loglevel>155</loglevel> <!-- log verbosity, 255 for very verbose, 0 for > quiet --> > > <conference xmlns="jabber:config:conference"> > <public/> <!-- rooms are public when created, comment to make them > private by default --> > <!-- the vCard section contains the vCard of the service --> > <vCard> > <FN>Public Chatrooms</FN> > <DESC>This service is for public chatrooms.</DESC> > <URL>http://foo.bar/</URL>; > </vCard> > <history>40</history> <!-- maximum numbers of history lines send when > joining a room --> > <logdir>/var/spool/jabberd/conference.localhost/logs/</logdir> <!-- > where to store the room logs, comment to disable logging --> > <!--logsubdirs/--> <!-- uncomment to stores the room logs in subdirs > (for example 2007/08/02) --> > <stylesheet>../style.css</stylesheet> <!--URL of the log stylesheet --> > <!-- default text to send to legacy clients, will also be used in the > logs --> > <notice> > <join>has become available</join> > <leave>has left</leave> > <rename>is now known as</rename> > </notice> > <!-- lists of admins of the service, add a <user/> tag by admin --> > <sadmin> > <user>admin@localhost</user> > </sadmin> > <dynamic/> > <!-- <persistent/> --> <!-- persistent rooms will be created, overide > <dynamic/> --> > <!-- <locknicks/> --> <!-- enforce the user nickname to the user part of > his jid --> > <!-- <roomlock/> --> <!-- uncomment to allow only admins to create rooms > --> > <hideempty/> > <!-- configuration of MySQL, only used if the MySQL exports is > activated, see README.sql --> > <!--<mysql> > <user>root</user> > <pass/> > <database>chat</database> > <host>localhost</host> > </mysql>--> > </conference> > </jcr> > > > > > > > > > > > > > Any idea what can be wrong? > > > Thanks! > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > I've finally solved it by enabling linux compatibility kernel module.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?hj6jqv$la2$1>