search

bornintelligent / google-breakpad

Automatically exported from code.google.com/p/google-breakpad
0 stars 0 forks source link

Breakpad does not work on Linux 64-bit OS (even using 32-bit build) #227

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I am running Fedora Core 6 on an AMD 64-bit processor.

When running the official 32-bit Firefox Beta 1 milestone, undecodable
crash reports are uploaded.

See
http://crash-stats.mozilla.com/report/index/716f79ab-985f-11dc-a95a-001a4bd43e5c
for an example report.

Original issue reported on code.google.com by wgianopo...@gmail.com on 22 Nov 2007 at 1:07

GoogleCodeExporter commented 9 years ago 
In Mozilla bug 427210 it has been reported that this works fine on and Intel 
64-bit
processor, so this is likely AMD64 only.

Original comment by wgianopo...@gmail.com on 5 Apr 2008 at 12:33

GoogleCodeExporter commented 9 years ago 
I attached a patch (this diff is for mozilla's breakpad tree).  sscanf() should 
use
"%Lx" instead of "%x".

Original comment by makoto...@gmail.com on 17 Jun 2008 at 3:13

Attachments:

GoogleCodeExporter commented 9 years ago 
Attempting to build src/client/linux/handler fails on 64-bit Linux (CentOS 5, 
Intel):

../../../client/linux/handler/linux_thread.h:152: error: 
‘user_fpxregs_struct’ has
not been declared
linux_thread.cc:238: error: ‘user_fpxregs_struct’ has not been declared
linux_thread.cc: In member function ‘int
google_breakpad::LinuxThread::ListModules(google_breakpad::CallbackParam<bool
(*)(const google_breakpad::ModuleInfo&, void*)>*) const’:
linux_thread.cc:311: warning: format ‘%x’ expects type ‘unsigned int*’, 
but argument
3 has type ‘uintptr_t*’
linux_thread.cc:311: warning: format ‘%x’ expects type ‘unsigned int*’, 
but argument
4 has type ‘uintptr_t*’
linux_thread.cc: In member function ‘bool
google_breakpad::LinuxThread::FindSigContext(uintptr_t, sigcontext**)’:
linux_thread.cc:405: error: ‘struct sigcontext’ has no member named 
‘ebp’
linux_thread.cc:408: error: ‘struct sigcontext’ has no member named 
‘ebp’

Original comment by ashoema...@gmail.com on 27 Oct 2008 at 5:20

GoogleCodeExporter commented 9 years ago 
ashoemaker: that's different, that's issue 239.

Original comment by ted.mielczarek on 27 Oct 2008 at 9:39

GoogleCodeExporter commented 9 years ago 
Seems to me the problem of empty crash reports on AMD64 should be fixed with my 
patch
from issue 299.

Original comment by r.peni...@gmail.com on 3 Mar 2009 at 1:45

GoogleCodeExporter commented 9 years ago 
I'm pretty sure this is fixed on trunk.

Original comment by ted.mielczarek on 9 Dec 2009 at 8:46