search

google / sawbuck

Automatically exported from code.google.com/p/sawbuck
107 stars 40 forks source link

File and Line are empty #53

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.  Performance trace from Chrome or regular trace from 3rd party application.

What is the expected output? What do you see instead?

Expect to see file name and line number per the sawbuck website screenshot and 
regular Chromium logging.

What version of the product are you using? On what operating system?

Sawbuck 0.6.8.0

logging_win.cc    79524
logging_win.h    126240

Windows XP, Windows 2008 (R1), Windows 2008 SP2.

Original issue reported on code.google.com by fnjo...@gmail.com on 24 May 2012 at 3:21

GoogleCodeExporter commented 8 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:

GoogleCodeExporter commented 8 years ago 
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

GoogleCodeExporter commented 8 years ago 
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