kicad-developers team mailing list archive

[Nick Østergaard <oe.nick@xxxxxxxxx>]

Hi, I was one of the persons able to recreate it earlier. I am on
archlinux x86_64, but I can't reproduce it on  6302 release/debug nor
6277 release now. I think I did reproduce the issue on 6277 release when I
previously tested it.  So I don't know it is needs some other
prerequisite for it to happen. I could reproduced 3 of 3 thimes on
each a debug and release build last time. hmm

@Andrew, I think your forgot to mention that it was only on the GAL
canvas, right?

2015-11-06 19:23 GMT+01:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
> On 11/6/2015 1:18 PM, Andrew Zonenberg wrote:
>> I'm on Debian 7 amd64. A couple of other people in #kicad managed to
>> reproduce the issue as well and I think most were linux based too.
>
> If this is the case and there is no report for this already, please
> submit one so we can track it.  I use Debain testing and will attempt to
> reproduce it on my system when I get a chance.  I doubt I'll have time
> to look at it today but I will have time over the weekend.
>
>>
>> On 06/11/15 09:34, jp charras wrote:
>>> Le 06/11/2015 18:25, Andrew Zonenberg a écrit :
>>>> There's another bug I spent a while hunting for earlier this
>>>> week, but couldn't get too far with. Maybe someone else can pick
>>>> it up?
>>>>
>>>> Steps to reproduce: * Open pad editor * Select pad type: SMT *
>>>> Select copper layers: none * Uncheck all technical layers
>>>>
>>>> In the debug build this will display a warning but keep running;
>>>> in release it aborts or crashes.
>>
>>> On Windows, I just have a warning message in a message box in
>>> OpenGL canvas and no issue in legacy mode, but no crash.
>>
>>> What is your OS ?
>>
>>>>
>>>> Although *exiting* the pad editor should not be allowed if the
>>>> pad has no layers at all (or possibly pop up a dialog asking if
>>>> the user wants to delete it?), having no layers selected should
>>>> be a legal intermediate state during editing of a pad stack.
>>>>
>>>> On 06/11/15 09:04, Mark Roszko wrote:
>>>>> One thing I didn't think was fixed yet was a null dereference
>>>>> introduced with the clipper library upgrade. jp fixed the
>>>>> uninitialized warnings but theres still a explicit null deref
>>>>> in a loop condition. CID 132144. What does it impact? No clue.
>>>>
>>>>> And speaking of pns, there is still CID 106401 where
>>>>> PNS_MEANDERED_LINE::MeanderSegment can memory leak.
>>
>>> They are only warnings.
>>
>>
>> _______________________________________________
>> 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
>>
>
>
> _______________________________________________
> 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