[bf1942] New build...
Greg
itooo at itooo.com
Fri Dec 13 09:19:16 EST 2002
run your program, when it segfaults it generates a .core file
run : gdb <exe file> <core file>
then: (gdb) where
thats it :)
--------------
Friday, December 13, 2002, 1:46:54 PM:
G> Just for the record.. How do I perform a stacktrace?
G> -------Original Message-------
G> From:bf1942 at icculus.org
G> Date: Friday, December 13, 2002 12:46:44
G> To:bf1942 at icculus.org
G> Subject: Re: [bf1942] New build...
G> IMHO it's very cool of Ryan to release builds in a short cycle. Like
G> this, problems with different libraries or OS's can be taken care of
G> sooner or at least be found sooner and thus get fixed sooner.
G> My guess is, that Ryan will incorporate a fix for the "no connect" bug
G> in the next release... so just play a round of tux racer and relax.
G> @ Alexander Staniura
G> It is not fair what you write! Go to the official BF homepage, do you
G> happen to see a downloadable version of the linux server there? I don't
G> think so... this beta test is for volunteers. If you want to volunteer,
G> please, join us and try to help Ryan with whatever you can do to help.
G> Just flaming and stupid comments are not the way to a stable server...
G> patience is. Give Ryan the time he needs and he'll give us the server
G> we want...
G> On Freitag, Dezember 13, 2002, at 01:36 Uhr, Andreas Grün
G> <ag at b-comp.de> wrote:
>> hi,
>>
>> its not ok to flame the developers in this public beta phase we are
>> undergoing. but IMHO it would be much more constructive, if any
>> further build
>> would be tested not to have the problem, that no player can connect,
>> before
>> releasing it to the community.
>>
>> hope to see some build like this.
>>
>> regards,
>>
>> andreas
>>
>>
>>
>> Am Freitag, 13. Dezember 2002 13:23 schrieb Peter Norin:
>>> do you know the purpose of a beta?... oh.. sorry no you dont...
>>>
>>> try to be constructive.. comments like this is totally braindead and
>>> does
>>> noone any good.
>>>
>>> /P
>>>
>>> -----Original Message-----
>>> From: Alexander Staniura [mailto:SantaHomer at web.de]
>>> Sent: den 13 december 2002 13:10
>>> To: bf1942 at icculus.org
>>> Subject: RE: [bf1942] New build...
>>>
>>>
>>> The new build is only codesalat, too.....
>>> Theyre too stupid to code an server that runs!
>>>
>>> -----Original Message-----
>>> From: bf1942-return-249-SantaHomer=web.de at icculus.org
>>> [mailto:bf1942-return-249-SantaHomer=web.de at icculus.org] On Behalf Of
>>> Greg
>>> Sent: Freitag, 13. Dezember 2002 12:43
>>> To: Ryan C. Gordon
>>> Subject: Re: [bf1942] New build...
>>>
>>> Gotta different stack trace than previously with this version:
>>>
>>> (gdb) where
>>> #0 0x08f644c8 in dice::ref2::MemoryPool::alloc () at eval.c:41
>>> #1 0x08f64558 in dice::ref2::MemoryPool::alloc () at eval.c:41
>>> #2 0x08f68ab4 in __builtin_vec_new () at eval.c:41
>>> #3 0x08b02473 in dice::meme::Memory::wstringDuplicate () at eval.c:41
>>> #4 0x08aed191 in dice::meme::WstringData::set () at eval.c:41
>>> #5 0x08b84fa3 in dice::bf::BfMenu::initHud () at eval.c:41
>>> #6 0x08b8ae7d in dice::bf::BfMenu::outputMessage () at eval.c:41
>>> #7 0x08ccfe5e in dice::bf::GameServer::handleGameEventManagerEvent ()
>>> at eval.c:41
>>> #8 0x08cd49e1 in dice::bf::GameServer::processReceivedPackets () at
>>> eval.c:41
>>> #9 0x08cc865a in dice::bf::GameServer::update () at eval.c:41
>>> #10 0x08a9eb31 in dice::bf::Setup::mainLoop () at eval.c:41
>>> #11 0x08a9e11c in dice::bf::Setup::start () at eval.c:41
>>> #12 0x08a81a4d in main () at eval.c:41
>>> #13 0x40076306 in __libc_start_main (main=0x8a81890 <main>, argc=1,
>>> ubp_av=0xbffffb74, init=0x8a80ca8 <_init>, fini=0x960211c <_fini>,
>>> rtld_fini=0x4000d2cc <_dl_fini>, stack_end=0xbffffb6c)
>>> at ../sysdeps/generic/libc-start.c:129
>>>
>>>
>>> Hope this helps...
>>> --------------
>>> Friday, December 13, 2002, 12:43:56 AM:
>>>
>>>
>>> RCG> Ok, guys, thanks for your patience. Try this one:
>>>
>>> RCG>
>>> http://icculus.org/betas/bf1942/bf1942-lnxded-betaupdate-build-
>>> 103973014
>>> 2.tar.bz2
>>>
>>> RCG> (that's a 6.6 meg download.)
>>>
>>> RCG> (I'm a big fan of long filenames...it's an overcompensation for
>>> my
>>> DOS 3.1
>>> RCG> days, I have no doubt.)
>>>
>>> RCG> This version should (knock on wood) fix all the segfaults...at
>>> least, it
>>> RCG> should fix all the ones that I got backtraces for. It will
>>> definitely fix
>>> RCG> the crash on map restart for those that got that far, and some
>>> other
>>> RCG> problems that were likely causing crashes on startup have been
>>> patched,
>>> RCG> too.
>>>
>>> RCG> That being said, I can't promise it will, since this will need
>>> more
>>> broad
>>> RCG> testing to sort it out. If you still experience crashes on
>>> startup
>>> and
>>> RCG> such, my apologies. Just let me know and we'll sort it out, but
>>> I'm
>>> more
>>> RCG> confident.
>>>
>>> RCG> To use, unpack the tarball over your old installation. It'll
>>> overwrite the
>>> RCG> binaries and the README with new versions. This is just an
>>> update,
>>> so
>>> RCG> you'll need the original tarball if you didn't have it already.
>>>
>>> RCG> Note that this is just focusing on this nasty crashes right now
>>> so
>>> that we
>>> RCG> can get around to more specific bug reports.
>>>
>>> RCG> Good luck, everyone.
>>>
>>> RCG> --ryan.
>>
>>
G> .
More information about the Bf1942
mailing list