Open GoogleCodeExporter opened 9 years ago
Screenshot also showing Google Update without file and line details.
Original comment by fnjo...@gmail.com
on 13 Jun 2012 at 4:11
Attachments:
Root cause discovered. Sawbuck is 32-bit and my logger is 64-bit, event
messages are passing one field with the size of a pointer.
http://src.chromium.org/viewvc/chrome/trunk/src/base/logging_win.cc?annotate=650
62#l80
http://code.google.com/p/sawbuck/source/browse/tags/release-0.6.8.0/sawbuck/log_
lib/log_consumer.cc#98
Original comment by fnjo...@gmail.com
on 14 Jun 2012 at 1:58
I guess the stack trace capture is causing the problem - what happens if you
turn stack trace capture off?
The way to fix this would be to define a separate message for 64-bit stack
traces, though there might also be some fallout in Sawbuck proper to store and
resolve 64 bit addresses.
A patch is more than welcome!
Original comment by siggi@chromium.org
on 14 Jun 2012 at 2:05
Original issue reported on code.google.com by
fnjo...@gmail.com
on 24 May 2012 at 3:21