[cod] Segmentation fault / gdb backtrace

Jared Bell jarbell at gmail.com
Thu Dec 6 10:19:28 EST 2007


Which Ubuntu version are you running? I am trying this on 7.10.

On Dec 6, 2007 5:36 AM, Sido - Callofduty.pl <sido.cod at gmail.com> wrote:

> I have a COD4 server running on Ubuntu - works great, without problems...
> Maybe try to setup new fresh Ubuntu server installation.
>
>
> 2007/12/6, Jared Bell < jarbell at gmail.com>:
>
> > Crashes on me as well under Ubuntu. Hopefully there's a fix or
> > workaround soon.
> >
> > On Dec 5, 2007 7:45 PM, Vadim Clyne-Kelly <vadimjnr at gmail.com> wrote:
> >
> > > I get that error on debian etch if gcc and binutils are installed.
> > > Some error wit debian and de librarys cod4 uses i think. I havnt got a
> > >
> > > reply on a fix yet, but in pretty sure its a cod4 bug.
> > >
> > > On 11/28/07, qizmo <qizmo85 at gmail.com> wrote:
> > > > gdb backtrace:
> > > >
> > > >
> > > > codservu at server:~/cod4-linux-server$ gdb cod4_lnxded-bin
> > > > GNU gdb 6.4.90-debian
> > > > Copyright (C) 2006 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 "i486-linux-gnu"...(no debugging symbols
> > > found)
> > > > Using host libthread_db library "/lib/tls/libthread_db.so.1".
> > > >
> > > > (gdb) run
> > > > Starting program: /home/codservu/cod4-linux-server/cod4_lnxded-bin
> > > > (no debugging symbols found)
> > > > (no debugging symbols found)
> > > > [Thread debugging using libthread_db enabled]
> > > > [New Thread -1210586816 (LWP 19508)]
> > > > (no debugging symbols found)
> > > > (no debugging symbols found)
> > > > (no debugging symbols found)
> > > > (no debugging symbols found)
> > > > (no debugging symbols found)
> > > > CoD4 MP 1.0 build linux-i386 Nov 21 2007
> > > >
> > > > Program received signal SIGSEGV, Segmentation fault.
> > > > [Switching to Thread -1210586816 (LWP 19508)]
> > > > 0xb7deb90d in memset () from /lib/tls/libc.so.6
> > > > (gdb) bt
> > > > #0  0xb7deb90d in memset () from /lib/tls/libc.so.6
> > > > #1  0x081a621b in std::char_traits<char>::eq ()
> > > > #2  0x08123374 in ?? ()
> > > > #3  0x08123e66 in ?? ()
> > > > #4  0x081d456e in std::char_traits<char>::eq ()
> > > > #5  0xb7d93ea8 in __libc_start_main () from /lib/tls/libc.so.6
> > > > #6  0x0804ac11 in ?? ()
> > > > (gdb)
> > > >
> > > >
> > > >
> > > > --
> > > > -----------------------------------------
> > > > Ville Valtonen
> > > > GSM: 040-8344825
> > > > ville at vallaton.net
> > > > -----------------------------------------
> > > >
> > >
> > >
> > > --
> > > Thanks,
> > > Vadim
> > >
> > > ---
> > > To unsubscribe, send a blank email to cod-unsubscribe at icculus.org
> > > Mailing list archives: http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?38
> > >
> > >
> > >
> >
>
>
> --
> www.callofduty.pl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/cod/attachments/20071206/c22ed5d0/attachment.htm>


More information about the Cod mailing list