Issue 20272 - ErrorReport of Windows build doesn't come up when soffice crashes
Summary: ErrorReport of Windows build doesn't come up when soffice crashes
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: configure (show other issues)
Version: OOo 1.1 RC5
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: khirano
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-28 15:13 UTC by khirano
Modified: 2006-03-14 21:02 UTC (History)
5 users (show)

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


Attachments
winenv.set (8.54 KB, text/plain)
2003-09-28 15:15 UTC, khirano
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description khirano 2003-09-28 15:13:36 UTC
Got a successful rc5 Windows build with configure switches
--enable-crashdump --enable-symbols=SMALL
but its ErrorReport doesn't come up when soffice is crashed by
http://www.openoffice.org/issues/show_bug.cgi?id=19717

Build Environment:
OS : Windows XP Professional SP1
Tool: Visual C++ 6.0 Enterprise Edition SP5
Microsoft Platform SDK : February 2003
shell : tcsh

configure option:
--with-lang=ENUS,JAPN
--with-jdk-home=/cygdrive/c/progra~1/java/j2sdk1.4.1_04 --with-dict=ALL
--with-use-shell=tcsh
--with-mspdb-path=/cygdrive/c/progra~1/micros~4/common/msdev98/bin
--with-ant-home=/usr/local/apache-ant-1.5.3-1 --enable-crashdump
--enable-symbols=SMALL

After installing this build, bootstrap.ini looks fine:
--------------------------------------------------------
[Bootstrap]
ProductKey=OpenOffice.org 1.1.0
Location=$SYSUSERCONFIG/sversion.ini
Section=Versions
BaseInstallation=$ORIGIN/..
UserInstallation=${$Location:$Section:$ProductKey}
buildid=645(Build:8693)
InstallMode=NETWORK
ProductPatch=

[ErrorReport]
ErrorReportPort=80
ErrorReportServer=report.services.openoffice.org
--------------------------------------------------------

winenv.set will be attached.
Comment 1 khirano 2003-09-28 15:15:16 UTC
Created attachment 9755 [details]
winenv.set
Comment 2 khirano 2003-09-28 15:32:57 UTC
After the installation of this build, looking into /program, I found
the following if compared with the recent official rc5 .

1) two files are missing:
487,424 2003/9/1 1:10 msvcp70.dll
344,064 2003/9/1 1:10 msvcr70.dll

2) different size of crashrep: 
this build:
16,452 2003/9/21 1:10 crashrep.com
53,324 2003/9/21 1:10 crashrep.exe
official build:
5,632 2003/9/1 1:10 crashrep.com
241,664 2003/9/1 1:10 crashrep.exe

Comment 3 Martin Hollmichel 2003-09-29 11:26:46 UTC
mh->hro: please have alook to it.
Comment 4 hennes.rohling 2003-09-30 09:50:47 UTC
So far I've no idea what went wrong. Regarding the file sizes this
looks like a broken build. Espacially the crashrep.exe is far to small. 
Perhaps the resources are missing or some changes where made to the
build environment that only affect VC6 compiler.
The official RC5 build was made with the VC .Net compiler.
Comment 5 quetschke 2003-09-30 22:29:04 UTC
Errm, I don't know if crashrep is supposed to work with MSVC6, but
in configure (see snippet):

dnl ===================================================================
dnl Windows builds with .NET need msvcp70.dll/msvcr70.dll in
external/msvcp70/
dnl ===================================================================
if test "$_os" = "WINNT" -a "$COMEX" = "8"; then
   AC_MSG_CHECKING([msvcp70.dll])
   if test -f ../external/msvcp70/msvcp70.dll -a -f
../external/msvcp70/msvcr70.dll; then
      AC_MSG_RESULT([found])
   else
      AC_MSG_ERROR([msvcp70.dll and/or msvcr70.dll are/is missing in
external/msvcp70/.
These dlls are part of the .NET installation and can be found in a
directory
similar to:
"c:\\Program Files\\Microsoft Visual Studio .NET\\Visual C++ .NET
Professional - English\\"
Please copy the files to external/msvcp70.])
   fi
fi

I introduced the tests only for a .NET build. Did anyone
ever try to use crashrep with a MSVC build?

(I can provide a build (also with the dlls from .NET) in a MSVC
build)
Comment 6 khirano 2005-01-30 13:13:08 UTC
We don't and may not use the tool MSVC6 anymore.
No problem with recent build tools and environments.
Comment 7 khirano 2005-01-30 13:17:31 UTC
We use the .Net tool and we have no problem with building recent builds.
Thanks.