Bug 561265 - [abrt] crash in NetworkManager-gnome-1:0.7.996-6.git20091021.fc12
[abrt] crash in NetworkManager-gnome-1:0.7.996-6.git20091021.fc12
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
12
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
abrt_hash:6af71f1c7ac308406d3e951c29f...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-02-03 03:30 EST by Rolle
Modified: 2010-02-09 15:56 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-02-09 15:56:59 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (1.41 KB, text/plain)
2010-02-03 03:30 EST, Rolle
no flags Details

  None (edit)
Description Rolle 2010-02-03 03:30:22 EST
abrt 1.0.4 detected a crash.

architecture: i686
cmdline: /usr/bin/nm-connection-editor
component: NetworkManager
executable: /usr/bin/nm-connection-editor
kernel: 2.6.31.5-127.fc12.i686
package: NetworkManager-gnome-1:0.7.996-6.git20091021.fc12
rating: 0
reason: Process was terminated by signal 11
release: Fedora release 12 (Constantine)

backtrace
-----
warning: core file may not match specified executable file.
Cannot access memory at address 0x84

Thread 1 (Thread 1901):
#0  0x08063be0 in routes_button_clicked_cb (button=<value optimized out>, 
    user_data=<value optimized out>) at page-ip4.c:601
        self = <value optimized out>
        dialog = 0xfffffffb
        toplevel = <value optimized out>
        automatic = <value optimized out>
        method = 0xfffffffb <Address 0xfffffffb out of bounds>
        __PRETTY_FUNCTION__ = "routes_button_clicked_cb"
        __func__ = "routes_button_clicked_cb"
#1  0x00dbcfd8 in ?? ()
No symbol table info available.
#2  0x087cd0f0 in ?? ()
No symbol table info available.
#3  0xfffffffb in ?? ()
No symbol table info available.
#4  0x088ee070 in ?? ()
No symbol table info available.
#5  0x08953d50 in ?? ()
No symbol table info available.
#6  0x00000002 in ?? ()
No symbol table info available.
#7  0x00000004 in ?? ()
No symbol table info available.
#8  0x00000003 in ?? ()
No symbol table info available.
#9  0x089237d8 in ?? ()
No symbol table info available.
#10 0x00c3abe7 in ?? ()
No symbol table info available.
#11 0x07a03a88 in ?? ()
No symbol table info available.
#12 0x00dadc9b in ?? ()
No symbol table info available.
#13 0x00de968c in ?? ()
No symbol table info available.
#14 0x089237d8 in ?? ()
No symbol table info available.
#15 0x00000000 in ?? ()
No symbol table info available.
Cannot access memory at address 0x84
Comment 1 Rolle 2010-02-03 03:30:25 EST
Created attachment 388473 [details]
File: backtrace
Comment 2 Dan Williams 2010-02-09 15:56:59 EST
Need more debuginfo on this one...

Note You need to log in before you can comment on or make changes to this bug.