Results 1 to 5 of 5

Thread: How to get info about crashing app?

  1. #1

    Default How to get info about crashing app?

    Hi all,

    I've installed quantum GIS on opensuse 11.3 gnome, so far so good. I run the app and it opens fine. To get the app to use data on the HD you get a dialogue box with a browse button. It should just be a case of clicking browse and selecting the required data file. Unfortunately when I click on browse the app crashes. I've no idea how to get info about the crash in an attempt to solve the problem. Had a similar problem with gimp in suse 11 kde could only fix it by updating the os to 11.3. It may be a lib issue but no idea what's the next move.

    Any help greatly appreciated.

  2. #2
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    17,037

    Default Re: How to get info about crashing app?

    On Tue, 30 Nov 2010 23:06:01 +0000, casperg wrote:

    > Hi all,
    >
    > I've installed quantum GIS on opensuse 11.3 gnome, so far so good. I run
    > the app and it opens fine. To get the app to use data on the HD you get
    > a dialogue box with a browse button. It should just be a case of
    > clicking browse and selecting the required data file. Unfortunately when
    > I click on browse the app crashes. I've no idea how to get info about
    > the crash in an attempt to solve the problem. Had a similar problem with
    > gimp in suse 11 kde could only fix it by updating the os to 11.3. It may
    > be a lib issue but no idea what's the next move.
    >
    > Any help greatly appreciated.


    I would start by launching the app from a terminal window and see if that
    tells you anything.

    If it doesn't, launch it under gdb - when it crashes, you'll be in gdb
    and can pull a stack trace for the developers to help diagnose what the
    cause is.

    Jim



    --
    Jim Henderson
    openSUSE Forums Administrator
    Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

  3. #3
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: How to get info about crashing app?

    Your first step can be to start the application from a terminal and watch
    the console output if it contains some usefull information after the crash.
    If that does not give you info next step can be to use gdb (debugger).

    --
    openSUSE 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.5 | GeForce
    9600 GT | 4GB Ram
    openSUSE 11.3 64 bit | Intel Core2 Duo T9300@2.50GHz | KDE 4.5 | Quadro FX
    3600M | 4GB Ram

  4. #4

    Default Re: How to get info about crashing app?

    Thanks for replies,

    I've posted some of the bug report bit it seems to be waiting for administrator approval...

    Thanks

    casper

  5. #5

    Default Re: How to get info about crashing app?

    I have posted the first part of the bug report below does it make any sense to anyone?

    System: Linux 2.6.34.7-0.5-default #1 SMP 2010-10-25 08:40:12 +0200 x86_64
    X Vendor: The X.Org Foundation
    X Vendor Release: 10800000
    Selinux: No
    Accessibility: Enabled
    GTK+ Theme: Sonar
    Icon Theme: Gilouche
    GTK+ Modules: canberra-gtk-module, gail:atk-bridge, gnomebreakpad

    Memory status: size: 800292864 vsize: 800292864 resident: 72486912 share: 45498368 rss: 72486912 rss_rlim: 18446744073709551615
    CPU usage: start_time: 1291218006 rtime: 151 utime: 136 stime: 15 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

    Backtrace was generated from '/usr/bin/qgis'

    [Thread debugging using libthread_db enabled]
    [New Thread 0x7f2dcf7fe710 (LWP 14162)]
    0x00007f2df84cfe7d in waitpid () from /lib64/libpthread.so.0
    #0 0x00007f2df84cfe7d in waitpid () from /lib64/libpthread.so.0
    #1 0x00007f2df6002189 in g_spawn_sync () from /usr/lib64/libglib-2.0.so.0
    #2 0x00007f2df60026c9 in g_spawn_command_line_sync ()
    from /usr/lib64/libglib-2.0.so.0
    #3 0x00007f2de89979f0 in ?? ()
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
    #4 <signal handler called>
    #5 0x00007f2de8fd1dbf in ?? () from /usr/lib64/libltdl.so.7
    #6 0x00007f2de8fd2f6e in ?? () from /usr/lib64/libltdl.so.7
    #7 0x00007f2de8fd37f9 in lt_dlopenadvise () from /usr/lib64/libltdl.so.7
    #8 0x00007f2de8fd38c9 in lt_dlopenext () from /usr/lib64/libltdl.so.7
    #9 0x00007f2de93eb458 in ?? () from /usr/lib64/libcanberra.so.0
    #10 0x00007f2de93eb9dc in ?? () from /usr/lib64/libcanberra.so.0
    #11 0x00007f2de93e42a8 in ?? () from /usr/lib64/libcanberra.so.0
    #12 0x00007f2de93e4e61 in ca_context_play_full ()
    from /usr/lib64/libcanberra.so.0


    This is the last part of the report

    No symbol table info available.
    #74 0x000000000053d47b in main ()
    No symbol table info available.
    A debugging session is active.

    Inferior 1 [process 14155] will be detached.

    Quit anyway? (y or n) [answered Y; input not from terminal]


    ----------- .xsession-errors (7 sec old) ---------------------
    (npviewer.bin:11710): Gdk-WARNING **: XID collision, trouble ahead
    (npviewer.bin:11710): Gdk-WARNING **: XID collision, trouble ahead
    *** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()
    Window manager warning: Invalid WM_TRANSIENT_FOR window 0x7400019 specified for 0x7400017 (qgis).
    Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3000019 specified for 0x3000017 (qgis).
    *** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()
    Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3000019 specified for 0x3000017 (qgis).
    sys:1: Warning: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
    ** (nautilus:2045): CRITICAL **: atk_object_initialize: assertion `ATK_IS_OBJECT (accessible)' failed
    Window manager warning: Invalid WM_TRANSIENT_FOR window 0x6a00019 specified for 0x6a00017 (qgis).
    *** nss-shared-helper: Shared database disabled (set NSS_USE_SHARED_DB to enable).
    *** nss-shared-helper: Shared database disabled (set NSS_USE_SHARED_DB to enable).
    Window manager warning: Invalid WM_TRANSIENT_FOR window 0x7000019 specified for 0x7000017 (qgis).
    --------------------------------------------------

    Thanks for the help guys but I think fixing this problem is beyond my knowledge.

    Cheers

    Casperg

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •