gEDA-user: gschem regularly segfaults on OpenBSD
I have gschem 20060123 When I edit schematics in gschem, I get randomly a segfault say every 5 minutes. I have to save every say 30 seconds and when it explodes, restart it and continue. I didn't have these problems on Linux. But the version I used there may have been different. I don't remember what was the last version of gschem I used on Linux. It doesn't depend on what schematic I edit. I think it may be caused by the protection of OpenBSD against malilcious code. OpenBSD kernel has some special measures incorporated which make sure that if the program damages the memory, it crashes as often as possible. CL ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: Bug when printing a schematic with pictures?
Hi all, I dug through the mailing list as best as I could, and did not find any specific mention of this issue, so I thought I would post here and see if anyone else is experiencing it or has a solution. I am running gschem version 20050820 on a Mac OSX machine. I realize this version is a tad out of date, but it is the newest package I could find that would work on the Mac with just a compile. Recently, I started using the picture insert feature in gschem to include a logo, which is composed of a graphic along with some text. The format of this logo is PNG, greyscale. I have also tested this bug with a greyscale jpeg, same results. The bug is that if you are not zoomed in on the picture when you go to 'print' the schematic to PostScript, the resulting picture in the PostScript ends up being blurry. That is to say, it seems that whatever viewing aspect you currently have determines what resolution the picture will have in the PostScript file. If you are fully zoomed out, the picture ends up to be blurry and unreadable. However, if I zoom in such that the picture fills the screen, then the embedded picture comes out completely clear. The rest of the schematic is not affected either way. Is this indeed a bug, or some kind of wacky feature? :) This zoom in workaround is OK for now, but slightly annoying. However, the picture insert feature is fantastic, though... I can provide some examples in case this was not very clear. Steve Ball Snurkle Engineering ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: gschem regularly segfaults on OpenBSD
On Wed, 2006-11-15 at 10:27 +0100, Karel Kulhavy wrote: I have gschem 20060123 Sorry,... I mis-read your version number. That is a fairly old version, and it sounds like you may be suffering the autosave crash. This was fixed in CVS on 2006-09-04, I think the latest release was 20061020. It is entirely possible that BSD makes the fairly rare autosave crash more repeatable. (Wish I'd known that when I was trying to track it down!) Regards Peter Clifton ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Increment drill size on 344 vias
The easiest way is with a perl/python script. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Increment drill size on 344 vias
David Carr wrote: Quick question: I have a board with 344 vias that I'd like to increase in size from 20 mils to 24 mils. Is there a way to do this semi-automatically in PCB? There are other vias of different sizes on the board. Maybe 'find and replace' over the section of your pcb with the vias. I've done this before and it's pretty painless. You could paste that section into another file and 'replace all'. or something. Phil ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Increment drill size on 344 vias
David Carr wrote: Quick question: I have a board with 344 vias that I'd like to increase in size from 20 mils to 24 mils. Select them and any other non-via objects, but not the other size vias somehow. Maybe multiple area selects or one big one or select all...depending... In the pcb command window give the command ChangeDrillSize(SelectedVias, 24, mil) and if you want to make the annulus bigger too... ChangeSize(SelectedVias,44,mil) The pcb commands will take only vias from the selected set and change them. John Griessen ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Increment drill size on 344 vias
On Wed, 15 Nov 2006 19:03:57 -0600 John Griessen [EMAIL PROTECTED] wrote: David Carr wrote: Quick question: I have a board with 344 vias that I'd like to increase in size from 20 mils to 24 mils. Select them and any other non-via objects, but not the other size vias somehow. Maybe multiple area selects or one big one or select all...depending... In the pcb command window give the command ChangeDrillSize (SelectedVias, 24, mil) and if you want to make the annulus bigger too... ChangeSize(SelectedVias,44,mil) The pcb commands will take only vias from the selected set and change them. That said, it _would_ be very helpful to have something else available except the +/- 10 mils fixed step (not only for holes, also for track widths etc). I would gladly sacrifice the +/- 10 options for a simple dialog which asks for a new size. It doesn't make much sense to decrease a 12 mil track by 10 mils anyway. I'm not too experienced a programmer, but I'm willing to help out... John ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Increment drill size on 344 vias
John Griessen wrote: David Carr wrote: Quick question: I have a board with 344 vias that I'd like to increase in size from 20 mils to 24 mils. Select them and any other non-via objects, but not the other size vias somehow. Maybe multiple area selects or one big one or select all...depending... In the pcb command window give the command ChangeDrillSize(SelectedVias, 24, mil) and if you want to make the annulus bigger too... ChangeSize(SelectedVias,44,mil) The pcb commands will take only vias from the selected set and change them. This all makes me wish more and more for a more powerful user programming capability in pcb and also gschem. Despite the pain which skill programming can be, this sort of thing would be trivial in cadence. It is fairly easy to iterate over a design and find instances of a certain type (a via in layout, an instance of a particular cell, whatever) and filter based on some property and then change things. Granted, I'm more likely to want this programming capability when dealing with hundreds of pages of schematics. Then again, 344 vias is not a small number. -Dan ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
