Description of problem: Edb just started without any speciall parameters. ------------------ Program received signal SIGSEGV, Segmentation fault. -----------------------------------------------------------------------------------------------------------------------[regs] RAX: 0x0000000000000000 RBX: 0x0000000000746960 RBP: 0x0000000000746978 RSP: 0x00007FFFFFFFD760 o d I t s Z a P c RDI: 0x0000000000000000 RSI: 0x4D4D580000000000 RDX: 0x0000000000B4B370 RCX: 0x000000344C7B7CE0 RIP: 0x00000000004215F5 R8 : 0x0000000000B4B330 R9 : 0x0000000000745850 R10: 0x0000000000000000 R11: 0x0000000000000000 R12: 0x0000000000BAFD60 R13: 0x0000000000000000 R14: 0x0000000000000000 R15: 0x0000000000000000 CS: 0033 DS: 0000 ES: 0000 FS: 0000 GS: 0000 SS: 002B -----------------------------------------------------------------------------------------------------------------------[code] => 0x4215f5 <_ZN13ArchProcessorC2Ev+69>: mov rax,QWORD PTR [rdi] 0x4215f8 <_ZN13ArchProcessorC2Ev+72>: call QWORD PTR [rax+0x20] 0x4215fb <_ZN13ArchProcessorC2Ev+75>: mov rdi,QWORD PTR [rip+0x325286] # 0x746888 <_ZN3edb2v113debugger_coreE> 0x421602 <_ZN13ArchProcessorC2Ev+82>: mov BYTE PTR [rbx+0x20],al 0x421605 <_ZN13ArchProcessorC2Ev+85>: movabs rsi,0x584d4d0000000000 ----------------------------------------------------------------------------------------------------------------------------- 0x00000000004215f5 in ArchProcessor::ArchProcessor() () gdb$ bt #0 0x00000000004215f5 in ArchProcessor::ArchProcessor() () #1 0x000000000043fffa in edb::v1::arch_processor() () #2 0x000000000044cbf5 in DebuggerMain::DebuggerMain(QWidget*) () #3 0x000000000041fa0c in main () Version-Release number of selected component: edb-0.9.18-10.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: edb crash_function: ArchProcessor::ArchProcessor executable: /usr/bin/edb kernel: 4.1.8-100.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 ArchProcessor::ArchProcessor at arch/x86_64/ArchProcessor.cpp:43 #1 edb::v1::arch_processor at Debugger.cpp:196 #2 DebuggerMain::DebuggerMain at DebuggerMain.cpp:232 #3 start_debugger at main.cpp:102 Potential duplicate: bug 814564
Created attachment 1083998 [details] File: backtrace
Created attachment 1083999 [details] File: cgroup
Created attachment 1084000 [details] File: core_backtrace
Created attachment 1084001 [details] File: dso_list
Created attachment 1084002 [details] File: environ
Created attachment 1084003 [details] File: exploitable
Created attachment 1084004 [details] File: limits
Created attachment 1084005 [details] File: maps
Created attachment 1084006 [details] File: open_fds
Created attachment 1084007 [details] File: proc_pid_status
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.