21 Sep
2004
21 Sep
'04
6:02 p.m.
Its an Athlon 64 3400+ system with 512MB of RAM.
[root@sip1 ser]# uname -a
Linux sip1 2.6.8-1.521 #1 Mon Aug 16 09:01:00 EDT 2004 x86_64 x86_64 x86_64
GNU/Linux
I had to modify lock_ops.h on line 66 to include the following otherwise it
would fail to compile:
#include <errno.h>
#include "dprint.h"
I would do the backtrace but ser doesn't seem to be generating a core file.
Is there some sort of option to make it do that?
----------------------------------------
Michael Shuler, C.E.O.
BitWise Communications, Inc. (CLEC) And BitWise Systems, Inc. (ISP)
682 High Point Lane
East Peoria, IL 61611
Office: (217) 585-0357
Cell: (309) 657-6365
Fax: (309) 213-3500
E-Mail: mike(a)bwsys.net
Customer Service: (877) 976-0711
-----Original Message-----
From: Andrei Pelinescu-Onciul
[mailto:pelinescu-onciul@fokus.fraunhofer.de]
Sent: Tuesday, September 21, 2004 3:28 PM
To: Michael Shuler
Cc: serusers(a)lists.iptel.org
Subject: Re: [Serusers] SER segfault on 64 bit
On Sep 21, 2004 at 14:27, Michael Shuler <mike(a)bwsys.net> wrote:
For some reason SER won't load on my 64 bit
Fedora Core 2
machines but it
will work fine on all of my other 32bit Fedora
Core 2
machines. Anyone know
if this a known problem with SER? I haven't
been able to
find any info on
it so I'm guessing I'm just doing
something wrong. Any
help would be
appreciated.
What kind of 64 bit machine are you using and what version of ser?
Could you send me the output of uname -m and a backtrace (gdb
ser core.*
and then bt)?
Andrei