Created a new module in the GAL module editor and made a pad, immediate
segfault. I think I was trying to open the pad properties when it
happened.
Using BZR 4996-product on Debian 7 amd64. I've saved a core dump
(/tmp/core.1386 on my machine... 682 MB so not going to upload it, if
anyone wants
It seems reproducible, happened three times in a row now. Steps to
reproduce:
1) Launch pcbnew
2) Switch to GAL view
3) Open module editor
4) Select my azonenberg library
5) Load module from library. My EIA_1206_CAP_NOSILK module is empty, I
created and saved it without adding any pads.
6) Click
On 15.07.2014 13:48, Andrew Zonenberg wrote:
Created a new module in the GAL module editor and made a pad, immediate
segfault. I think I was trying to open the pad properties when it
happened.
Using BZR 4996-product on Debian 7 amd64. I've saved a core dump
(/tmp/core.1386 on my machine... 682
Same thing happens to me if I switch to OpenGL, open the module editor,
create a new module, add a pad, and try to edit the properties.
Ubuntu 13.04, BZR 4992, using the inbuilt GPU on a core i3 -- relevant
output of lshw is:
description: VGA compatible controller
product: 3rd Gen
If you're using wx 2.8 (same as me) Orson has managed to come up with a
reproducible test case and is investigating.
On Wed, 2014-07-16 at 01:08 +1200, Blair Bonnett wrote:
Same thing happens to me if I switch to OpenGL, open the module
editor, create a new module, add a pad, and try to edit
On 15.07.2014 15:10, Andrew Zonenberg wrote:
If you're using wx 2.8 (same as me) Orson has managed to come up with a
reproducible test case and is investigating.
News from Orson: it looks like the order of redraw/canvas resize events
differs between wx versions (in 2.8 the compositor was
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
On 07/15/2014 03:14 PM, Tomasz Wlostowski wrote:
On 15.07.2014 15:10, Andrew Zonenberg wrote:
If you're using wx 2.8 (same as me) Orson has managed to come up with a
reproducible test case and is investigating.
News from Orson: it looks like the order of redraw/canvas resize events
differs
Le 14/07/2014 16:51, Maciej Sumiński a écrit :
Dear Developers,
After a period of testing, the module-editor branch [1] has just been
merged to the product branch. Besides the conversion of the module
editor to GAL
Thanks.
There is a redraw/refresh issue on Windows only (using wxWidgets
On 07/15/2014 04:57 PM, Nick Østergaard wrote:
Hi all
Just FYI, orson has been working hard today, and he has looking into
those and other bugs, and fixed them. Thank you Maciej.
1. fixed in 4997
2. fixed in 5001
3. not really a bug, just non intuitive for me
4. not a bug
5. no new update yet
See http://ci.kicad-pcb.org/job/kicad-qa/221/changes
Changes:
[jean-pierre charras] dialog non copper zones: better look. dialog copper
zones: fix a minor bug.
--
Started by an SCM change
Building in workspace http://ci.kicad-pcb.org/job/kicad-qa/ws/
$
See http://ci.kicad-pcb.org/job/kicad-qa/222/changes
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help :
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 :
On 16 July 2014 02:16, Maciej Sumiński maciej.sumin...@cern.ch wrote:
On 07/15/2014 03:14 PM, Tomasz Wlostowski wrote:
On 15.07.2014 15:10, Andrew Zonenberg wrote:
If you're using wx 2.8 (same as me) Orson has managed to come up with a
reproducible test case and is investigating.
News
14 matches
Mail list logo
