I was using the latest snapshot from sourceforge. I haven't used the
other development snapshots before this one.
I'll give cvs a try as soon as I have some time.
Any idea where to look in the source for the incoming object recording
*feature*, so I can manually hack it out on my build?
Quoting Tom Russo <[EMAIL PROTECTED]>:
On Mon, Jul 28, 2008 at 10:41:44PM -0400, we recorded a
bogon-computron collision of the <[EMAIL PROTECTED]> flavor,
containing:
I have been playing with xastir lately, and besides noticing the
newest development version crashing everytime I change settings on
interfaces. I have tested this with recent stable and development
versions.
Curt's already answered the other part of your post (while I was typing up
my own answer to it), but didn't address this one. This concerns me, and
I haven't had a similar experience and I run xastir on a three different
machines in different configurations (internet-only, kiss TNC with internet
interfaces, d700 mobile).
What platform are you using (i.e. operating system, hardware, etc.)? And by
"newest development version" do you mean a recent development
snapshot or CVS?
Pinning down your crashes to specific actions should help isolate
it. Perhaps
with CVS we can even pin down when the bug got introduced if someone can
reproduce the bug.
--
Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/
Tijeras, NM QRPL#1592 K2#398 SOC#236 AHTB#1
http://kevan.org/brain.cgi?DDTNM
"Argue for your limitations and sure enough, they're yours." -- R. Bach
_______________________________________________
Xastir mailing list
[email protected]
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
_______________________________________________
Xastir mailing list
[email protected]
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
