In any case we can conclude that it is not a static destructor issue I think.
Since we don't get to the end of main().
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://lau
http://lifecs.likai.org/2011/10/debugging-static-object-destruction.html
was found by googling for "debug static destructors".
But this is jumping the gun. The question still needs to get answered first.
Should you need to go down that path, I am not sure you need to use a Debug
build.
However
main is in wx/app.h, because this is where IMPLMENT_APP is defined.
Try the attached patch, after applying, modify printf() to your different
output function
if that is appropriate.
Any output text after "end of main" are coming from static destructors. If you
don't see
that output, then the
Thanks - although I did stray from the winbuilder toolchain - I quickly
migrated back. This error has existed since my initial builds before
changing toolchains. The wxPython build dir is restored from winbuilder's
distribution.
Regards,
Jason
On Mon, Jul 14, 2014 at 9:52 AM, Dick Hollenbeck
On 07/14/2014 03:14 AM, Jason Whiteman wrote:
> Thanks again. I had already added the suggested OnExit printfs directly
> after sending my
> previous message as I had mentioned the coverage was not full.
>
> int OnExit() // overload wxApp virtual
> {
> int jwdebug; // JW Debug
>
Jason,
The other thing to keep in mind is that you cannot mix C++ compilers within the
pcbnew
process. So if you are using wxPython, which was compiled with a particular
C++
toolchain, you have to keep using that same exact toolchain for the rest of
KiCad.
The same limitation does not pertai
Thanks again. I had already added the suggested OnExit printfs directly
after sending my previous message as I had mentioned the coverage was not
full.
int OnExit() // overload wxApp virtual
{
int jwdebug; // JW Debug
OutputDebugString(TEXT("single_top.cpp: OnExit() - Before
w
No idea.
I don't see the crash in the output. It would be prudent to have the crash
text and the
debug text in the same stream if possible, that way it might infer "sequence of
events".
There's not much remaining in program execution before the end. The only
additional
printf()'s you might a
I've been busy with other work - but wanted to offer an update.
For debugging the crash - the PGM_KICAD entries do not apply since
Kicad.exe itself does not crash - just pcbnew.I do not see that pcbnew
uses the PGM_KICAD exit routines here - as PGM_KICAD destroyers work fine
with kicad.exe.
G
Hi Jason,
Winbuilder doesn't currently support a debug version build. It's not a
good development environment, but it does at least give you the
dependencies you need to build KiCad on Windows successfully.
The problem with the debug build is with Python as Python searches for
different module na
I'm Linux fluent and prefer the unix environment but other constraints keep
Windows as my primary operating system which pulls Kicad in the Windows
direction. I could VM to Kicad - but I'd rather continue down the Windows
path. Looking long-term, the issues associated with Windows tend to argue
f
Le 06/07/2014 19:04, Dick Hollenbeck a écrit :
>>>
>>> Is there advice on how to get the debug to work w/winbuilder?
>
>
> I don't know winbuilder. However I would guess that its usefulness for a
> "developer" is
> diminished after installation of the toolchain and the goodies.
>
> After
>>
>> Is there advice on how to get the debug to work w/winbuilder?
I don't know winbuilder. However I would guess that its usefulness for a
"developer" is
diminished after installation of the toolchain and the goodies.
After that you will have to become master of:
1) CMake,
2) bzr, and
On 07/05/2014 08:23 PM, Jason Whiteman wrote:
> Team,
>
> I've been using the "printf" method to identify the cause of a windows
> exception on
> close of pcbnew.exe (release) I have seen. However, all passed for as deep
> to the end of
> the program as I could identify.
I maintain about
Team,
I've been using the "printf" method to identify the cause of a windows
exception on close of pcbnew.exe (release) I have seen. However, all
passed for as deep to the end of the program as I could identify.
Therefore, I wanted to transition to a debug build and use debug tools to
attemp
15 matches
Mail list logo
