Re: [asterisk-users] Asterisk won't start - trap invalid opcode

2012-01-04 Thread A J Stiles 
On Wednesday 04 January 2012, Duncan Turnbull wrote:
> Hi there
> 
> Happy New Year
> 
> I have a new install of asterisk 1.8.8.1 on ubuntu server
> 3.0.0-14-server #23-Ubuntu SMP Mon Nov 21 20:49:05 UTC 2011 x86_64 x86_64
> x86_64 GNU/Linux
> 
> It has a Sangoma A200 card and I thought should be fairly standard but I
> have a new error when trying to start asterisk and I don't really know
> where to start
> 
> Initially asterisk was installed with dahdi from a package but sangoma
> didn't seem happy. Once I added dahdi from source sangoma wanpipe
> installed okay, but when I reloaded asterisk it stopped. So I removed all
> the packages (I believe I have but something could be hanging around) and
> rebuilt asterisk from source. Same errors.
> 
> The only errors I can see are limited - I also stopped wan router and dahdi
> and I still get ~# asterisk -cvv
> Illegal instruction
> 
> Which isn't very informative. Kind of a fun challenge but not one I need
> right now
> 
> Google hasn't been able to find a similar issue

For what it's worth, I once tried installing Asterisk on an old VIA C7 box; 
and it turns out that this processor, while detecting as an i686, doesn't 
implement the full i686 instruction set -- and Asterisk is trying to use one 
of the non-implemented instructions.  Solution was to re-compile for i586.

It's just possible that something similar is going on here -- maybe your 
processor isn't implementing an instruction that Asterisk or Dahdi is relying 
on.  (It's my understanding that 64-bit processors don't fully implement the 
32-bit instructions when in 64-bit mode, but I wouldn't swear to that.)  Or 
maybe it's a library path problem -- something trying to use a 32-bit library 
instead of a 64-bit one, or vice versa.  Try ldd on the binaries.

What is your output from `cat /proc/cpuinfo` ?


If you have at least two SIP phones and/or an IAX route, try disabling Dahdi, 
and see if you can persuade Asterisk to run like that.  At least that should 
help track the problem down to one layer (Asterisk or Dahdi).

-- 
AJS

Answers come *after* questions.

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] Asterisk won't start - trap invalid opcode

2012-01-04 Thread Duncan Turnbull 
On 4/01/2012, at 11:47 PM, A J Stiles wrote:


> 
> For what it's worth, I once tried installing Asterisk on an old VIA C7 box; 
> and it turns out that this processor, while detecting as an i686, doesn't 
> implement the full i686 instruction set -- and Asterisk is trying to use one 
> of the non-implemented instructions.  Solution was to re-compile for i586.
> 

Thanks very much AJ

That did appear as one of the few google comments I found but I couldn't figure 
out whether it applies 

The outputs are below if you can interpret them, I can see lm in the cpu proc 
info but don't know how to check for better compatibility

> It's just possible that something similar is going on here -- maybe your 
> processor isn't implementing an instruction that Asterisk or Dahdi is relying 
> on.  (It's my understanding that 64-bit processors don't fully implement the 
> 32-bit instructions when in 64-bit mode, but I wouldn't swear to that.)  Or 
> maybe it's a library path problem -- something trying to use a 32-bit library 
> instead of a 64-bit one, or vice versa.  Try ldd on the binaries.
> 
ldd -v /usr/sbin/asterisk 
linux-vdso.so.1 =>  (0x7fff407ff000)
libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 
(0x7f72accc)
libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 
(0x7f72ac911000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f72ac571000)
libxml2.so.2 => /usr/lib/libxml2.so.2 (0x7f72ac216000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f72ac012000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f72abdf4000)
libtinfo.so.5 => /lib/libtinfo.so.5 (0x7f72abbcd000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f72ab949000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f72ab72d000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f72ab515000)
/lib64/ld-linux-x86-64.so.2 (0x7f72acf1b000)

Version information:
/usr/sbin/asterisk:
libdl.so.2 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libdl.so.2
libresolv.so.2 (GLIBC_2.2.5) => 
/lib/x86_64-linux-gnu/libresolv.so.2
libxml2.so.2 (LIBXML2_2.6.0) => /usr/lib/libxml2.so.2
libxml2.so.2 (LIBXML2_2.4.30) => /usr/lib/libxml2.so.2
libcrypto.so.1.0.0 (OPENSSL_1.0.0) => 
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
libm.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libm.so.6
libpthread.so.0 (GLIBC_2.3.3) => 
/lib/x86_64-linux-gnu/libpthread.so.0
libpthread.so.0 (GLIBC_2.2.5) => 
/lib/x86_64-linux-gnu/libpthread.so.0
libc.so.6 (GLIBC_2.8) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.3) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.4) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.3.2) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.3.4) => /lib/x86_64-linux-gnu/libc.so.6
libssl.so.1.0.0 (OPENSSL_1.0.0) => 
/lib/x86_64-linux-gnu/libssl.so.1.0.0
/lib/x86_64-linux-gnu/libssl.so.1.0.0:
libc.so.6 (GLIBC_2.4) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.3.4) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libc.so.6
libcrypto.so.1.0.0 (OPENSSL_1.0.0) => 
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0:
libdl.so.2 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libdl.so.2
libc.so.6 (GLIBC_2.3) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.7) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.4) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.3.4) => /lib/x86_64-linux-gnu/libc.so.6
/lib/x86_64-linux-gnu/libc.so.6:
ld-linux-x86-64.so.2 (GLIBC_2.3) => /lib64/ld-linux-x86-64.so.2
ld-linux-x86-64.so.2 (GLIBC_PRIVATE) => 
/lib64/ld-linux-x86-64.so.2
/usr/lib/libxml2.so.2:
libz.so.1 (ZLIB_1.2.2.3) => /lib/x86_64-linux-gnu/libz.so.1
libdl.so.2 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libdl.so.2
libm.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libm.so.6
libc.so.6 (GLIBC_2.7) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.4) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.3.2) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.3.4) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.3) => /l

Re: [asterisk-users] Asterisk won't start - trap invalid opcode

2012-01-04 Thread Duncan Turnbull 
I loaded the latest 1.6 which gets slightly further and a core dump shows this, 
but its past my ability to interpret

# gdb -se "asterisk" -c core | tee /tmp/backtrace.txt
GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /usr/sbin/asterisk...done.
[New LWP 19322]
[New LWP 19323]
[New LWP 19324]
[New LWP 19325]
[New LWP 19326]

warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Core was generated by `asterisk -d -g -cvvv'.
Program terminated with signal 4, Illegal instruction.
#0  0x00500eab in tzload (name=, sp=0x1fc7950, 
doextend=1) at stdtime/localtime.c:424
424 static int tzload(const char *name, struct state * const sp, const int 
doextend)



On 5/01/2012, at 12:13 AM, Duncan Turnbull wrote:

> On 4/01/2012, at 11:47 PM, A J Stiles wrote:
> 
> 
>> 
>> For what it's worth, I once tried installing Asterisk on an old VIA C7 box; 
>> and it turns out that this processor, while detecting as an i686, doesn't 
>> implement the full i686 instruction set -- and Asterisk is trying to use one 
>> of the non-implemented instructions.  Solution was to re-compile for i586.
>> 
> 
> Thanks very much AJ
> 
> That did appear as one of the few google comments I found but I couldn't 
> figure out whether it applies 
> 
> The outputs are below if you can interpret them, I can see lm in the cpu proc 
> info but don't know how to check for better compatibility
> 
>> It's just possible that something similar is going on here -- maybe your 
>> processor isn't implementing an instruction that Asterisk or Dahdi is 
>> relying 
>> on.  (It's my understanding that 64-bit processors don't fully implement the 
>> 32-bit instructions when in 64-bit mode, but I wouldn't swear to that.)  Or 
>> maybe it's a library path problem -- something trying to use a 32-bit 
>> library 
>> instead of a 64-bit one, or vice versa.  Try ldd on the binaries.
>> 
> ldd -v /usr/sbin/asterisk 
>   linux-vdso.so.1 =>  (0x7fff407ff000)
>   libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 
> (0x7f72accc)
>   libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 
> (0x7f72ac911000)
>   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f72ac571000)
>   libxml2.so.2 => /usr/lib/libxml2.so.2 (0x7f72ac216000)
>   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f72ac012000)
>   libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
> (0x7f72abdf4000)
>   libtinfo.so.5 => /lib/libtinfo.so.5 (0x7f72abbcd000)
>   libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f72ab949000)
>   libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
> (0x7f72ab72d000)
>   libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f72ab515000)
>   /lib64/ld-linux-x86-64.so.2 (0x7f72acf1b000)
> 
>   Version information:
>   /usr/sbin/asterisk:
>   libdl.so.2 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libdl.so.2
>   libresolv.so.2 (GLIBC_2.2.5) => 
> /lib/x86_64-linux-gnu/libresolv.so.2
>   libxml2.so.2 (LIBXML2_2.6.0) => /usr/lib/libxml2.so.2
>   libxml2.so.2 (LIBXML2_2.4.30) => /usr/lib/libxml2.so.2
>   libcrypto.so.1.0.0 (OPENSSL_1.0.0) => 
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
>   libm.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libm.so.6
>   libpthread.so.0 (GLIBC_2.3.3) => 
> /lib/x86_64-linux-gnu/libpthread.so.0
>   libpthread.so.0 (GLIBC_2.2.5) => 
> /lib/x86_64-linux-gnu/libpthread.so.0
>   libc.so.6 (GLIBC_2.8) => /lib/x86_64-linux-gnu/libc.so.6
>   libc.so.6 (GLIBC_2.3) => /lib/x86_64-linux-gnu/libc.so.6
>   libc.so.6 (GLIBC_2.4) => /lib/x86_64-linux-gnu/libc.so.6
>   libc.so.6 (GLIBC_2.3.2) => /lib/x86_64-linux-gnu/libc.so.6
>   libc.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libc.so.6
>   libc.so.6 (GLIBC_2.3.4) => /lib/x86_64-linux-gnu/libc.so.6
>   libssl.so.1.0.0 (OPENSSL_1.0.0) => 
> /lib/x86_64-linux-gnu/libssl.so.1.0.0
>   /lib/x86_64-linux-gnu/libssl.so.1.0.0:
>   libc.so.6 (GLIBC_2.4) => /lib/x86_64-linux-gnu/libc.so.6
>   libc.so.6 (GLIBC_2.3.4) => /lib/x86_64-linux-gnu/libc.so.6
>   libc.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libc.so.6
>   libcrypto.so.1.0.0 (OPENSSL_1.0.0) => 
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
>   /lib/x86_64-linux-gnu/libcrypto.so.1.0.0:
>

Re: [asterisk-users] Asterisk won't start - trap invalid opcode

2012-01-04 Thread A J Stiles 
On Wednesday 04 January 2012, Duncan Turnbull wrote:
> I loaded the latest 1.6 which gets slightly further and a core dump shows
> this, but its past my ability to interpret
> 
> # gdb -se "asterisk" -c core | tee /tmp/backtrace.txt
> GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08
> Copyright (C) 2011 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
>  This is free software: you are free to
> change and redistribute it. There is NO WARRANTY, to the extent permitted
> by law.  Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> For bug reporting instructions, please see:
> ...
> Reading symbols from /usr/sbin/asterisk...done.
> [New LWP 19322]
> [New LWP 19323]
> [New LWP 19324]
> [New LWP 19325]
> [New LWP 19326]
> 
> warning: Can't read pathname for load map: Input/output error.
> [Thread debugging using libthread_db enabled]
> Core was generated by `asterisk -d -g -cvvv'.
> Program terminated with signal 4, Illegal instruction.
> #0  0x00500eab in tzload (name=, sp=0x1fc7950,
> doextend=1) at stdtime/localtime.c:424 424static int tzload(const char
> *name, struct state * const sp, const int doextend)

It's a bit beyond my depth too, but I'd start with a look at localtime.c in 
the Asterisk source tree.  It might simply be trying to include something that 
isn't present on your system.

If you stick a /* harmless comment */ in this file and re-save it, this will 
give the file a new modification time.  Then run `make` again.  It will 
recompile just localtime.c  (this being the only source file that has changed 
since the last time make was run)  -- now watch very closely for errors.


Answers come *after* questions.

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] Asterisk won't start - trap invalid opcode

2012-01-04 Thread Steve Edwards 

On Wed, 4 Jan 2012, A J Stiles wrote:


If you stick a /* harmless comment */ in this file and re-save it, this will
give the file a new modification time.  Then run `make` again.  It will
recompile just localtime.c  (this being the only source file that has changed
since the last time make was run)  -- now watch very closely for errors.


The 'touch' command will update the file's access and modification times* 
without the risk of trashing something in the file.


*) Command line parameters can select just the access or the modification 
time. The default is both.


--
Thanks in advance,
-
Steve Edwards   sedwa...@sedwards.com  Voice: +1-760-468-3867 PST
Newline  Fax: +1-760-731-3000

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
  http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] Asterisk won't start - trap invalid opcode

2012-01-04 Thread Duncan Turnbull 
On 5/01/2012, at 8:06 AM, Steve Edwards wrote:

> On Wed, 4 Jan 2012, A J Stiles wrote:
> 
>> If you stick a /* harmless comment */ in this file and re-save it, this will
>> give the file a new modification time.  Then run `make` again.  It will
>> recompile just localtime.c  (this being the only source file that has changed
>> since the last time make was run)  -- now watch very closely for errors.
> 
> The 'touch' command will update the file's access and modification times* 
> without the risk of trashing something in the file.
> 
> *) Command line parameters can select just the access or the modification 
> time. The default is both.
> 

Touch seemed safer but I didn't see any errors

:/usr/src/asterisk-1.6.2.22# make
   [CC] stdtime/localtime.c -> stdtime/localtime.o
   [LD] abstract_jb.o acl.o adsistub.o aescrypt.o aeskey.o aestab.o alaw.o 
app.o ast_expr2.o ast_expr2f.o asterisk.o astfd.o astmm.o astobj2.o audiohook.o 
autoservice.o bridging.o callerid.o cdr.o channel.o chanvars.o cli.o config.o 
cryptostub.o datastore.o db.o devicestate.o dial.o dns.o dnsmgr.o dsp.o enum.o 
event.o features.o file.o fixedjitterbuf.o frame.o fskmodem.o 
global_datastores.o hashtab.o heap.o http.o image.o indications.o io.o 
jitterbuf.o loader.o logger.o manager.o md5.o netsock.o pbx.o plc.o poll.o 
privacy.o rtp.o say.o sched.o sha1.o slinfactory.o srv.o ssl.o 
stdtime/localtime.o strcompat.o strings.o taskprocessor.o tcptls.o tdd.o term.o 
test.o threadstorage.o timing.o translate.o udptl.o ulaw.o utils.o version.o 
xml.o xmldoc.o editline/libedit.a db1-ast/libdb1.a -> asterisk
 +- Asterisk Build Complete -+
 + Asterisk has successfully been built, and +
 + can be installed by running:  +
 +   +
 +make install   +
 +---+

I haven't found anything obvious in the debug stuff although I am not familiar 
enough to be sure 

Thanks very much

Unless there is something obvious I am thinking I will revert to either an 
earlier OS or maybe 32 bit - although that seems excessive

Cheers Duncan

> -- 
> Thanks in advance,
> -
> Steve Edwards   sedwa...@sedwards.com  Voice: +1-760-468-3867 PST
> Newline  Fax: +1-760-731-3000
> 
> --
> _
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>  http://www.asterisk.org/hello
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>  http://lists.digium.com/mailman/listinfo/asterisk-users


--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] Asterisk won't start - trap invalid opcode

2012-01-04 Thread James Cloos 
> "DT" == Duncan Turnbull  writes:

DT> I have a new install of asterisk 1.8.8.1 on ubuntu server 
DT> 3.0.0-14-server #23-Ubuntu SMP Mon Nov 21 20:49:05 UTC 2011 x86_64 x86_64 
x86_64 GNU/Linux

DT> The only errors I can see are limited - I also stopped wan router and dahdi 
and I still get 
DT> ~# asterisk -cvv
DT> Illegal instruction

What does /proc/cpuinfo say?  (Just the first chunk is enough.)

Try running asterisk is gdb:

:; gdb asterisk

(gdb) run -cvvddd

When it dies, try:

(gdb) bt full

(gdb) disasemble /m

You may also want to recompile asterisk after turing on:

DONT_OPTIMIZE
DEBUG_THREADS
BETTER_BACKTRACES

in the Compiler Flags section of make menuselect.

The gdb output if you do that may be more comprehensible.

Either way run gdb from the asterisk src directory.

When you find the point where it crashed, you can discover what the
illegal instruction is.

I suspect your compile may expect a more recent cpu than you have, and
may use sse instructions which it doesn't support.  A disassembly around
the failing instruction will confirm whether that is true and which
instruction it is.

-JimC
-- 
James Cloos  OpenPGP: 1024D/ED7DAEA6

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] Asterisk won't start - trap invalid opcode

2012-01-04 Thread Duncan Turnbull 

On 5/01/2012, at 12:21 PM, James Cloos wrote:

>> "DT" == Duncan Turnbull  writes:
> 
> DT> I have a new install of asterisk 1.8.8.1 on ubuntu server 
> DT> 3.0.0-14-server #23-Ubuntu SMP Mon Nov 21 20:49:05 UTC 2011 x86_64 x86_64 
> x86_64 GNU/Linux
> 
> DT> The only errors I can see are limited - I also stopped wan router and 
> dahdi and I still get 
> DT> ~# asterisk -cvv
> DT> Illegal instruction
> 
> What does /proc/cpuinfo say?  (Just the first chunk is enough.)
> 
> Try running asterisk is gdb:
> 
>:; gdb asterisk
> 
>(gdb) run -cvvddd
> 
> When it dies, try:
> 
>(gdb) bt full
> 
>(gdb) disasemble /m
> 
> You may also want to recompile asterisk after turing on:
> 
>DONT_OPTIMIZE
>DEBUG_THREADS
Hi James

I think the DONT_OPTIMIZE flag made a difference, the system is not crashing 
anymore

I am going to test it, and see if its really back, the other detail looked 
fairly similar to the core dump output in previous emails but there wasn't 
anything I could easily discern

I will let you all know how it turns out - thanks everyone

Cheers Duncan

>BETTER_BACKTRACES
> 
> in the Compiler Flags section of make menuselect.
> 
> The gdb output if you do that may be more comprehensible.
> 
> Either way run gdb from the asterisk src directory.
> 
> When you find the point where it crashed, you can discover what the
> illegal instruction is.
> 
> I suspect your compile may expect a more recent cpu than you have, and
> may use sse instructions which it doesn't support.  A disassembly around
> the failing instruction will confirm whether that is true and which
> instruction it is.
> 
> -JimC
> -- 
> James Cloos  OpenPGP: 1024D/ED7DAEA6


--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users