Okay, thanks. That stack trace doesn't look complete. Could you please post the full stack trace of a debug build of MITK and MITK-ProjectTemplate?

Maybe you are hitting this? http://lists.debian.org/debian-glibc/2011/01/msg00074.html

- Sascha

On 10/04/2012 09:55 PM, Federico Milano wrote:
I'm using an Ubuntu 10.04, g++ 4.4.3, Qt 4.6.2 (Ubuntu repository). The app is not printing the log location. I've built everything with the same built type, and both MITK and Project-Template are up-to-date. The stack trace:

Program received signal SIGSEGV, Segmentation fault.
_dl_fixup (l=<value optimized out>, reloc_arg=<value optimized out>)
    at dl-runtime.c:147
147dl-runtime.c: No such file or directory.
in dl-runtime.c

I think the error has something to do with missing dependencies, but I also, maybe naively, think that it is strange to get a segmentation fault because of a missing dependency.

thanks,

Federico

On Thu, Oct 4, 2012 at 4:43 PM, Sascha Zelzer <[email protected] <mailto:[email protected]>> wrote:

    Hi,

    can you please provide more information about your system (OS,
    compiler version, Qt version, etc.)?

    Also make sure to build both projects with the same build type
    (Release, Debug, etc.) if you are on Windows. The same applies for
    Qt if you have build it yourself.

    Make sure that the MITK and Project-Template build is up-to-date.

    If you still get crashes, please send us the log file. Its
    location is printed to the console when the application starts. If
    you have a debug build, run the AwesomeApp with a debugger and
    send us the stack trace of the crash.

    Thanks,
    Sascha


    On 10/04/2012 09:22 PM, Federico Milano wrote:

        Hi. This is probably a very basic question. I have compiled
        the actual version (c487ee3bbf2025b492e93ce06818e3aa9187ffdb)
        of MITK. Then, I've downloaded the template project and, since
        I had already built MITK, I compiled it without the
        superbuild. Everything compiles fine, but when I try to run
        the AwesomeApp, it runs for about 15 seconds and then it
        produces a segmentation fault message, without any other error
        messages.
        Could you give me any hint about what could be producing this
        problem?

        Thanks,

        Federico




------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to