On Sun, 19 Jun 2005 17:26:30 -0400 (EDT) [EMAIL PROTECTED] (Stuart Brorson) wrote:
> > I think all these remaining WARNINGS likely have to do with the initial > > theme problems and have nothing to do with a need for some > > code castings in gpcb. > > Meebe. The warnings which worry me are these: > > (pcb-bin:3146): GLib-GObject-CRITICAL **: file gsignal.c: line 2122 > (g_signal_emit_valist): assertion `G_TYPE_CHECK_INSTANCE (instance)' > failed > > (pcb-bin:3146): GLib-GObject-WARNING **: invalid (NULL) pointer > instance I said that because I never saw warnings like this (not even during any of the development time), but I'm really just speculating that it's because of the theme problem and definitely agree it should be tracked down. If you run pcb under gdb and then start it running with: (gdb) run xxx.pcb -g-fatal-warnings the run will abort at the first Gtk or Glib warning and you can get a stack backtrace, but with the theme warnings coming first, it makes it more difficult to isolate the later stuff. Sometimes I resort to sprinkling printf()'s to isolate in those situations, but what you should be able to do is set a breakpoint on g_log and then gdb will break each time a message is printed out. When you get to the critical ones, do a stack trace. Don't use "-g-fatal-warnings" in this case. So you would: $ gdb pcb (gdb) b g_log ...here gdb will say g_log is not defined and should the breakpoint be made pending? Say yes. (gdb) run xxx.pcb Each time gdb breaks, hit 'c' to continue until you get to the message you want, then: (gdb) bt And hopefully the stacktrace will give a clue about what to try next! It might also help if you can note what pcb was doing when the warnings appear. > FWIW, I am running Fedora Core 2 on the machine spewing these errors. > I will try FC3 later this evening. > > In any event, I'd like to track at least the last two down, because > the amount is spewage is quite large, and noobies running gEDA on > something other than a well-configured Debian box (yes, there are lots > of non-Debian systems out there) might be scared off. [1] I'll spend > some quality time looking. . . . . > > Stuart > > [1] I do not mean to disparage your totally awesome work with gPCB, > by the way! When I first showed gattrib to Ales it also spewed lots > of warnings. Ales -- in his infinite goodness -- helped me eliminate > almost all of the problems. I'd like to at least try to help somebody > else in the same way. Oh for sure do what it takes to flush out bugs or make it better! I'm only a bit frustrated at not knowing how to reproduce what you're getting. I did just move my theme engine out of the way and got the theme warnings to appear, but so far none of the later warnings. Bill
