Re: [Kicad-developers] Segfault that just started happening
Hi Simon, Thast was it. GLXInfo crashed also. I rebooted and it all came good. Not sure what the problem was with OpenGL. Thanks for the help. Steven On 31/10/18 9:11 pm, Simon Richter wrote: Hi, On 31.10.2018 14:42, Strontium wrote: The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 8548 error_code 2 request_code 154 minor_code 24) The segmentation fault happens because the error handler for X errors tries to exit the program, and stumbles over invalid objects there. This is an error path that is badly tested, because these errors are usually difficult to reproduce, so I'd ignore the segmentation fault here and focus on the X error. The major request code (154) is dynamically allocated, so it is difficult to tell which X extension caused it. The most likely candidate is GLX, where minor opcode 24 is X_GLXCreateNewContext. Do other OpenGL based programs work for you? Does glxinfo report Direct Rendering to be active? Simon ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] MacOS dependencies and minimum version
Last night our automated builds that build on 10.11 both failed because the latest version of our dependencies no longer builds on 10.11. How much time should we put into this, rather than move the builds to 10.12 and leave the 10.11 users where they're at? Apple does not announce end of life, but if they follow what they've done in the past, there will be no more security updates for 10.11 now that 10.14 is released. Adam ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Cairo printing
Just to let you know: I have just rebased and merged the Cairo printing support. Cheers, Orson On 10/7/18 1:53 PM, Maciej Sumiński wrote: > I have finished printing code refactor to take advantage of GAL in > pcbnew and gerbview [1]. This branch together with GALified > eeschema should cure GTK3-related headaches and lead us straight to 5.1. > In the meantime I will also try to port eeschema to the > new printing system for the sake of completeness, though it is not > critical for 5.1. > > I have tested the code on Linux x86_64, Windows 7 x86_64 and macOS > 10.13.4, but additional testing is welcome. > > Cheers, > Orson > > 1. https://code.launchpad.net/~orsonmmz/kicad/+git/kicad/+ref/cairo_printing > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > signature.asc Description: OpenPGP digital signature ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] [PATCH] In-memory string io_benchmark and some docs
Hey John, Your updated patch builds on windows so I went ahead and merged it. Hopefully it wont be an issue on any other build platforms. Thanks, Wayne On 10/30/2018 7:31 AM, John Beard wrote: > Hi Wayne, > > On Mon, Oct 29, 2018 at 6:16 PM Wayne Stambaugh wrote: >> >> Patches 2 and 3 are merged. I merge the fixed patch when you post it. > > Freshly Jenkins'ed for your consideration. > > Cheers, > > John > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Segfault that just started happening
Hi, On 31.10.2018 14:42, Strontium wrote: >> The error was 'BadValue (integer parameter out of range for operation)'. >> (Details: serial 8548 error_code 2 request_code 154 minor_code 24) The segmentation fault happens because the error handler for X errors tries to exit the program, and stumbles over invalid objects there. This is an error path that is badly tested, because these errors are usually difficult to reproduce, so I'd ignore the segmentation fault here and focus on the X error. The major request code (154) is dynamically allocated, so it is difficult to tell which X extension caused it. The most likely candidate is GLX, where minor opcode 24 is X_GLXCreateNewContext. Do other OpenGL based programs work for you? Does glxinfo report Direct Rendering to be active? Simon signature.asc Description: OpenPGP digital signature ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Segfault that just started happening
Extra Information: The following crash with the X segfault, schematic editor, symbol editor, pcb layout editor, footprint editor. And when they do, they kill the project browser. Gerber viewer also crashes with an X segfault, but i doesn't crash the project browser when it does. Bitmap to component, PCB calculator and Page layout editor all seem fine. On 31/10/18 20:42, Strontium wrote: I was on the js-reynaud legacy nightly ppa (Ubuntu 18.04), and things were fine a few days ago. But i just tried to run kicad and it was crashing. So, i uninstalled everything from legacy nightly and installed the ppa js-reynaud/kicad-5 but for some reason if i try and open a schematic OR a pcb, it crashes with a segfault also: Trying to open a schematic: steven@steven-ge40:~$ kicad The program 'kicad' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 8548 error_code 2 request_code 154 minor_code 24) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Segmentation fault (core dumped) Trying to open a PCB: steven@steven-ge40:~$ kicad The program 'kicad' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 4479 error_code 2 request_code 154 minor_code 24) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Segmentation fault (core dumped) Anyone else seen this??? I have no idea what's going on. Steven ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] Segfault that just started happening
I was on the js-reynaud legacy nightly ppa (Ubuntu 18.04), and things were fine a few days ago. But i just tried to run kicad and it was crashing. So, i uninstalled everything from legacy nightly and installed the ppa js-reynaud/kicad-5 but for some reason if i try and open a schematic OR a pcb, it crashes with a segfault also: Trying to open a schematic: steven@steven-ge40:~$ kicad The program 'kicad' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 8548 error_code 2 request_code 154 minor_code 24) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Segmentation fault (core dumped) Trying to open a PCB: steven@steven-ge40:~$ kicad The program 'kicad' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 4479 error_code 2 request_code 154 minor_code 24) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Segmentation fault (core dumped) Anyone else seen this??? I have no idea what's going on. Steven ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] [PATCH] Verify wxPython.h exists.
Hey Orson, Thanks! I've been really busy and just didn't get a chance to merge it. Cheers, Wayne On 10/31/2018 5:42 AM, Maciej Sumiński wrote: > Hi Wayne, > > I have eventually checked the patch on Linux and Windows 7 as well and > it works as advertised, so I pushed it. Thank you for your contribution > to KiCad;) > > Cheers, > Orson > > On 10/29/18 1:33 PM, Maciej Sumiński wrote: >> Hi Wayne, >> >> KiCad with your patch applied builds fine on macOS 10.13.6, so it looks >> like you got the paths right. >> >> Cheers, >> Orson >> >> On 10/22/18 11:11 PM, Wayne Stambaugh wrote: >>> I created a patch to fix bug report 1785663. It works on linux and >>> windows msys2 builds. On these platforms wxPython.h is located in the >>> same path as the wx headers so it's straight forward fix. I'm not sure >>> where wxPython.h is installed on other build platforms. I would like >>> our macos and msvc devs to test it to make sure it doesn't break those >>> platform builds. >>> >>> Thanks, >>> >>> Wayne >>> >>> [1]: https://bugs.launchpad.net/kicad/+bug/1785663 > > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] [PATCH] Verify wxPython.h exists.
Hi Wayne, I have eventually checked the patch on Linux and Windows 7 as well and it works as advertised, so I pushed it. Thank you for your contribution to KiCad;) Cheers, Orson On 10/29/18 1:33 PM, Maciej Sumiński wrote: > Hi Wayne, > > KiCad with your patch applied builds fine on macOS 10.13.6, so it looks > like you got the paths right. > > Cheers, > Orson > > On 10/22/18 11:11 PM, Wayne Stambaugh wrote: >> I created a patch to fix bug report 1785663. It works on linux and >> windows msys2 builds. On these platforms wxPython.h is located in the >> same path as the wx headers so it's straight forward fix. I'm not sure >> where wxPython.h is installed on other build platforms. I would like >> our macos and msvc devs to test it to make sure it doesn't break those >> platform builds. >> >> Thanks, >> >> Wayne >> >> [1]: https://bugs.launchpad.net/kicad/+bug/1785663 signature.asc Description: OpenPGP digital signature ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
