kicad-developers team mailing list archive

[Jason Whiteman <whitemanjason@xxxxxxxxx>]

     I've tried a few different things with mixed results:

1) Tried moving the build environment to a new machine - entails:
     a. Starting fresh on a new machine with no other related build
environments
     b. Downloaded and un-7z'd the latest winbuilder (3.4-2)
     c. Built from scratch with default parameters including SCRIPTING ON
     d. Machine is Win Server 2008 R2

     Results:

     R1.1: Running on Win2k8 R2 - RunKicad.bat fails as Kicad.exe failed
with a 0xC0000005 error in wxbase300u_gcc_cm.dll

*Problem signature: *

Problem Event Name: APPCRASH

Application Name: kicad.exe

Application Version: 0.0.0.0

Application Timestamp: 0473ae68

Fault Module Name: wxbase300u_gcc_cm.dll

Fault Module Version: 3.0.0.0

Fault Module Timestamp: 52ce8e9f

Exception Code: c0000005

Exception Offset: 000af358

OS Version: 6.1.7601.2.1.0.400.8

Locale ID: 1033

Additional Information 1: 4c0d

Additional Information 2: 4c0d4d78887f76d971d5d00f1f20a433

Additional Information 3: 4c0d

Additional Information 4: 4c0d4d78887f76d971d5d00f1f20a433

     R1.2: Copied the root directory (including RunKicad), root/env (and
all subdirectories - for RunKicad), and root/bin (and all subdirectories)
to the original Win7 machine.  The wxbase error did not present itself, but
pcbnew.exe still failed in the same manner as the original compile on the
win7 machine - "shared library" failure.

     Conclusions: compile/build is not as much as the issue, not a
single-unit (toolchain land) failure.

2) Used SCRIPTING OFF to disable features that may be causing problems with
the shared library issue
     a. Modified KiCadWinbuilder.cmake - changed "set( SCRIPTING ON )" to
"set( SCRIPTING OFF )" as the sledge-hammer fix.

     Results:

     R2.1: Loading Kicad.exe (using RunKicad) on Win2k8 server failed the
same as R1.1 - still see wxbase error.
     R2.2: Copying over binaries from Win2k8 to Win7 (as R1.2 above) and
retried -- no longer see "shared library" failure.

     Conclusions: with loss of functionality, using SCRIPTING OFF will
allow the binaries to work on my Win7 machine.  However, the specific cause
of the failure (missing component, etc) is not identified.

      Secondly, the new/broken behavior of the binaries on Win2k8 is
troubling as it appears only a lucky target windows machine has allowed for
me to run these binaries.

Regards,
Jason



On Fri, Jun 27, 2014 at 12:40 PM, Dick Hollenbeck <dick@xxxxxxxxxxx> wrote:

> On 06/27/2014 12:01 PM, Brian Sidebotham wrote:
> > Hi Guys,
> >
> > I should first say, this is not typical of Winbuilder. Both pcbnew and
> > cvpcb work fine for me on a fresh Windows 7 install using the github
> > fp-lib-table. So there's clearly something different about your setup.
> >
> > Process monitor is (from sysinternals) is excellent at tracking
> > dependency loading, so if you want to track what's getting loaded from
> > where, that's the best tool for the job. If you use dependency walker
> > make sure you run it from the console provided by enterenv.bat so that
> > PATH is set the same as when kicad is run.
>
>
> Brian, thanks for your involvement.  I am now bowing out.  I just wanted
> us to remember
> that it loads and runs fine under pcbnew.exe, and not kicad.exe.
>
> Your comment about setting the environment differently probably pertains
> to the difference
> in loading results also.  Perhaps there's a difference in how the
> environment is setup for
> the specific process.
>
> Remember that the environment when the process runs, is what's critical.
>  A batch file can
> add or remove settings to the environment that it starts with, before the
> process runs.
> So simply getting a snapshot from the registry is not necessarily
> sufficient to describe
> the runtime environment variable values that any particular process sees.
>
> Environment varialbe "PATH" is still my biggest suspicion, in concert with
> a difference in
> launching methodology.
>
> Out,
>
> Dick
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>