Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#9979 closed Bug report (fixed)

v3.10.0_rc1, SIGSEGV, crash on load

Reported by: Joseph DeVore Owned by:
Priority: critical Component: FileZilla Client
Keywords: SIGSEGV, crash, Cc:
Component version: Operating system type: Windows
Operating system version: Windows 7 SP1 Ultimate 64bit

Description

Total crash, I just installed the update from Beta 2 to rc1
and it crashes instantly... there isn't much to tell I even tried passing it through GNU debugger but it did have anything usable without debugging symbols...

Fault bucket 753968117, type 17

Faulting application name: filezilla.exe, 
version: 3.10.0.0, 
time stamp: 0x00000006

Faulting module name: filezilla.exe, 
version: 3.10.0.0, 
time stamp: 0x00000006

Exception code: 0xc0000005
Fault offset: 0x009c4d87
Faulting process id: 0xdb8
Faulting application start time: 0x01d026edf8cbe7ad

Faulting application path: 
C:\Program Files (x86)\FileZilla\filezilla.exe

Faulting module path: 
C:\Program Files (x86)\FileZilla\filezilla.exe

Report Id: 46d125af-92e1-11e4-afcd-001e33825849
Program received signal SIGSEGV, Segmentation fault.

0x00dc4d87 in ?? ()

(gdb) bt
#0  0x00dc4d87 in ?? ()
#1  0x004a5b1a in ?? ()
#2  0x004a66b8 in ?? ()
#3  0x005a115b in ?? ()

[Inferior 1 (process 3512) exited with code 030000000005]

I am attaching the windows Error report file
its a txt file so any text editor should be able to read it...

but... WinDbg is helpful O_o

(47c.228): Break instruction exception - code 80000003 (first chance)

I take it you forgot to remove a break point lol.... O_o

Attachments (2)

AppCrash_filezilla.exe_393f8733c4cf5178fff3cdad914ca45d1ca85_0e552146__Report.wer (5.9 KB ) - added by Joseph DeVore 9 years ago.
Debugging (gdb)_Filezilla.cmd (648 bytes ) - added by Joseph DeVore 9 years ago.

Download all attachments as: .zip

Change History (6)

by Joseph DeVore, 9 years ago

comment:1 by Joseph DeVore, 9 years ago

Resolution: fixed
Status: newclosed

as of v3.10.0_rc2
its working again so I will goahead and close it myself as long as Tim Doesn't mind.

comment:2 by Joseph DeVore, 9 years ago

Summary: v3.10.0_rc1, SIGSEGV, crash and will not loads at all.v3.10.0_rc1, SIGSEGV, crash on load, (some one forgot to remove a break point loi)

comment:3 by Tim Kosse, 9 years ago

Summary: v3.10.0_rc1, SIGSEGV, crash on load, (some one forgot to remove a break point loi)v3.10.0_rc1, SIGSEGV, crash on load

The breakpoint you see is auto-generated by the error handling infrastructure in response to the segfault.

comment:4 by Joseph DeVore, 9 years ago

ooh... so it wasn't a break point a dev forgot to remove? hm.....
well rc2 loaded fine like normal so I figured that was the case so closed my report..

Note: See TracTickets for help on using tickets.