Issue 16009 - Crashreport doesn't contain library names and symbolic information
Summary: Crashreport doesn't contain library names and symbolic information
Status: CLOSED FIXED
Alias: None
Product: porting
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 RC
Hardware: PC Windows XP
: P2 Trivial (vote)
Target Milestone: OOo 1.1 RC
Assignee: Martin Hollmichel
QA Contact: issues@porting
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-24 14:23 UTC by stx123
Modified: 2004-02-07 10:09 UTC (History)
7 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description stx123 2003-06-24 14:23:06 UTC 
In Crashreport (Report-Mail 1.0) are library names not mentioned.
Comment 1 hennes.rohling 2003-06-25 09:58:32 UTC 
Investigating.
Comment 2 hennes.rohling 2003-06-25 10:10:00 UTC 
StarOffice installs dbghelp.dll version 6.1 while currently OOo used
version 5.1 from Windows XP system directory.
Windows API documentation is wrong: dbghelp.dll version 5.1 does not
provide a full qualified path for the library name of each stack frame.
Comment 3 stx123 2003-06-25 12:04:11 UTC 
I'm running Windows XP Professional Version 2000 with dbghlp.dll
version 5.1. With 645_m8s1 (build 8643) the stracktraces contain DLL
names (includng pathes).
Fixed?
Comment 4 hennes.rohling 2003-06-27 16:13:44 UTC 
MH has updated scp so that dbghelp.dll 6.1 is installed with OOo.
Therefor it works.
Comment 5 Joost Andrae 2003-07-01 19:04:59 UTC 
JA: using dbghelp.dll from the system doesn't give necessary
information but when using a more recent version I get useful
information: verified in ooo11rc cws
Comment 6 stx123 2003-07-04 10:12:57 UTC 
Hi, I have to reopen this issue for OOo 1.1rc.
Crashreports generated on my Windows XP system don't provide symbolic 
information. Other versions (645m9s3) do. So it seems not a question 
of system configuration.
I think, receiving useful crashreport data is essential for our RC 
and would consider this as showstopper.
Greetings, Stefan
Comment 7 quetschke 2003-07-04 10:37:24 UTC 
I'm feeling like Don Quixote and the Windmills! (issue, mail and IRC)

See issue 14472.

Apply the c_o2.diff, and use the new --enable-crashdump switch
when you call configure.

Or just add a line with

(unix)
setenv ENABLE_CRASHDUMP "yes"

(4nt)
set ENABLE_CRASHDUMP=yes

to your *env.set|bat file

And rebuild!
Comment 8 hennes.rohling 2003-07-04 11:42:05 UTC 
Martin's fix to install dbghelp.dll ver 6.1.17.2 did not take place.
The dbghelp.dll is not copied into the program directory and therefor
the incomplete dbghelp.dll from the system is used.
Comment 9 stx123 2003-07-04 11:48:52 UTC 
As said earlier, I have the up-to-date dbghelp.dll and it still
doesn't work for me.
Comment 10 stx123 2003-07-04 11:49:29 UTC 
I don't think dbghelp.dll is the root cause.
See earlier comments.
Comment 11 Martin Hollmichel 2003-07-04 12:08:05 UTC 
dbghelp is fixed by 16406.
Comment 12 stx123 2003-07-04 12:48:42 UTC 
Together with hro we were able to clarify, that
- access to pdb files will reveal symbolic info in reports
- a dbghelp more recent than version 5.1 is needed at the the client
(if no pdb available)

I close this issue and reopen 16009
Comment 13 stx123 2003-07-04 12:56:00 UTC 
To help QA I would like to mention, that you can see whether
crashreports are usefull by triggering a crash and then have a look at
the report.
There must be a value in the name field of the stack information:
<errormail:StackInfo pos="4" ip="0x101241B1" rel="0x001241B1"
ordinal="Ordinal5991+0x000005F1" name="vcl645mi.dll"
path="C:\Programme\OpenOffice.org1.1rc\program\"/>
Comment 14 stx123 2003-07-04 12:56:44 UTC 
reassigning to mh
Comment 15 Martin Hollmichel 2003-07-11 10:36:46 UTC 
fixed in ooo11rc2
Comment 16 Martin Hollmichel 2004-02-07 10:07:36 UTC 
mark as verified.
Comment 17 Martin Hollmichel 2004-02-07 10:09:38 UTC 
close issue.