| ID: | 6383 |
| From: | John Wehle <jo...@feith.com> |
| Date: | Tue, 23 Jul 2024 02:16:33 -0400 (EDT) |
| Subject: | Re: [pcb-rnd] freebsd zoom crash (was: Re: pcb-rnd doesn't support geda pcb files after 20110603) |
> What do you mean by console? The virtual console for the machine where operating system messages are logged. Not the shell I used to start pcb-rnd. > > Currently my console shows: > > > > pid 1609 (scc_62520), jid 0, uid 0: exited on signal 6 (core dumped) > > pid 1645 (scc_52843), jid 0, uid 0: exited on signal 3 (core dumped) > > pid 1669 (scc_16815), jid 0, uid 0: exited on signal 8 (core dumped) > > pid 1681 (scc_61913), jid 0, uid 0: exited on signal 11 (core dumped) > > I'm asking because these messages looks like coming from scconfig, > ... > That's why you see different singals for different pids, all running from > scc_* test programs. If there's a core dump in ./, that should be in > scconfig/. You would be correct ... there are core dumps in the scconfig directory so not related to the actual zoom problem. > > Unfortunately I don't (at the moment) know how to duplicate the problem > > on demand. Most of the time pcb-rnd zooms in fine / without issue. > > The trigger may depend on your data. If it's not something gtk/opengl/X > related, the most probable thing is one of the "check what's under the > mouse cursor" hooks (e.g. edit-point or the hover-over-pad note printout). > > So there are two ways to narrow this down: > ... I'll keep that in mind ... thanks. -- John
Reply subtree:
6383 Re: [pcb-rnd] freebsd zoom crash (was: Re: pcb-rnd doesn't support geda pcb files after 20110603) from John Wehle <jo...@feith.com>