Segmentation fault

A few minutes ago, simon crashed. Here is the report. I don’t know yet how to create useful crash reports. I will figure that out later.

At least I can say that simon was able to recognize the word überflutender (SAMPA: y: b ah f l u: t @ n d ah). So it works. I am not sure which sound card is beeing used (I used two microphones at the same time: on-board sound card and USB sound card).

Tags: , , ,

5 Responses to “Segmentation fault”

  1. Peter Grasch says:

    Don’t worry, crash reports are not really useful at the current development stage anyways.

    I have to wonder, tough: Are you using the scenario branch or plain old trunk?

    Trunk is the last kind-of-stable version, the bleeding edge version can be found at branches/scenarios (VERY experimental).

    Greetings,
    Peter

  2. producer says:

    Hello Peter!

    Until now, I using just plain old trunk.

    I would like to check out the scenario branch because I would like to take a look at ssc/sscd. Is it possible to install both (plain old trunk and scenario branch) on the same computer? Or would it be better to use two different computers?

    Greetings,
    Ralf

  3. Peter Grasch says:

    Well you could use different install prefixes but that is a bit of work (especially with plugins).

    But you can always do a cd trunk/build && make uninstall && cd ../../branches/scenarios/build && make install and the other way around to switch between the two.

    However, you might get problems with shared files (~/.kde/share/apps/simon and ~/.kde/share/apps/simond). Make sure to backup them before you switch between the two.

    Of course using two computers would work two.

    Greetings,
    Peter

  4. Peter Grasch says:

    s/two/too/

  5. producer says:

    Thanks for the info. I think that I will install the scenarios branch on a different computer.