re floating point exception

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: re floating point exception
From: raoul.megelas (raoul.megelas_AT_libertysurf.fr)
Date: Fri Mar 21 2003 - 19:20:24 EET


On Thu, 20 Mar 2003, Kai Vehmanen wrote:
On Thu, 20 Mar 2003, raoul.megelas wrote:

> > to say that mlockall and munlockall are not yet implemented

i> Hmm, does the configure process fail...? :o It should go through fine even
> though mlockall is not found (although you will get the "can't lock
> memory" warnings on runtime).

in config.h i found:
#define HAVE_MLOCKALL 1
#define HAVE_MUNLOCKALL 1
after configure command.

> > now about the -y:100 without defining a chainsetup, i have the same
> > bihaviour

  this is another problem!

> > but i cann't say anythin about this because i have a big problem as follows:
> > ecasound -c -i:somefile.wav -o:/dev/dsp
> > floating point exception handling.
> > here's the gdb loading and backtrace

> Hmm, what architecture (x86, i64, etc?) and what compiler version? I'd
> suggest tryign compiling without -ffast-math (see configure.in:70).

i386 on FreeBSD 5.0 (CURRENT)
Without -ffast-math does nothing, please see latter

> > Reading symbols from /usr/libexec/ld-elf.so.1...done.
> > Loaded symbols for /usr/libexec/ld-elf.so.1
> > #0 0x2834f197 in _thread_stack_alloc () from /usr/lib/libc_r.so.5
> > (gdb) backtrace
 
> > #0 0x2834f197 in _thread_stack_alloc () from /usr/lib/libc_r.so.5
> > #1 0x2834dff5 in pthread_create () from /usr/lib/libc_r.so.5
> > #2 0x080ccbed in ecasound_setup_signals (state=0x820a020) at ecasound.cpp:400
> > #3 0x080cb93a in main (argc=4, argv=0xbfbff7ac) at ecasound.cpp:93
> > #4 0x080cb865 in _start ()

> By the way, this just provides info for one thread. You need to switch
> to the offending thread with "thread x", where x is the thread id. You can
> get a list of different threads with "info threads". Once in the right
> thread, then "bt" as usual. If you don't know which is the offending one,

Thanks for the info but there is only one thread at this time.
it seams that the last call is:
 pthread_create at 400 (here).
  I know that certain parameters are for return values.
Are the other values what one does expect?

        *state:
{console = 0x0, control = 0x0, logger = 0x0,
 eciserver = 0x0, session = 0x0, daemon_thread = 0x0,
lock = 0, exit_request = 0, ret_val = 0, daemon_mode = false,
_cerr_output_only_mode = false, interactive_mode=false, quiet_mode = false}.

 watchdog type = thread{<incomplete type>}*

ecasound_watchdog_thread: void *(void *).

in case of a different implementation of pthread_create here is the syntax
for FreeBSD 5.0:

LIBRARY
        reentrant C Library (libc_r, -lc_r)

SYNOPSIS
        #include <pthread.h>

        int pthread_create(pthread_t *thread, const pthread_attr_t
        *attr, void *(* start_routine)(void*), void *arg);

Best regards

        raoul
        raoul.megelas_AT_libertysurf.fr


New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Fri Mar 21 2003 - 19:09:42 EET