]> jfr.im git - irc.git/blame - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/000719.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2002 / 000719.html
CommitLineData
3bd189cb
JR
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2<HTML>
3 <HEAD>
4 <TITLE> [IRCServices Coding] nick.db - Invalid Format
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20nick.db%20-%20Invalid%20Format&In-Reply-To=3CE68F4A.2080602%40unirc.net">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="000718.html">
11 <LINK REL="Next" HREF="000690.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices Coding] nick.db - Invalid Format</H1>
15 <B>Russell Garrett</B>
16 <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20nick.db%20-%20Invalid%20Format&In-Reply-To=3CE68F4A.2080602%40unirc.net"
17 TITLE="[IRCServices Coding] nick.db - Invalid Format">rg at tcslon.com
18 </A><BR>
19 <I>Sat May 18 10:58:28 PDT 2002</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="000718.html">[IRCServices Coding] nick.db - Invalid Format
22</A></li>
23 <LI>Next message: <A HREF="000690.html">[IRCServices Coding] Re: Chanserv problem with .33?
24</A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#719">[ date ]</a>
27 <a href="thread.html#719">[ thread ]</a>
28 <a href="subject.html#719">[ subject ]</a>
29 <a href="author.html#719">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33<!--beginarticle-->
34<PRE>On Sat, 2002-05-18 at 18:28, Brendan Bowden wrote:
35&gt;<i> I'm getting the same kind of thing using bahamut-1.4.33 and
36</I>&gt;<i> ircserv-a33... seemingly random segfaults followed by a corrupted
37</I>&gt;<i> nick.db. Any hints on how I can get this bug tracked down?
38</I>
39Recompile services with the -dumpcore option passed to configure (if it
40isn't already - can we have this enabled by default in the alpha/beta?),
41then wait for services to segfault and you should have a core file in
42the same directory as the ircservices executable.
43
44Feed it into gdb like this:
45
46gdb /path/to/ircservices /path/to/core
47
48gdb will spew out lots of rubbish, followed by a (gdb) prompt - type
49'bt', then grab the resulting trace and post it to the list.
50
51Russ Garrett (<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">russ at garrett.co.uk</A>)
52
53
54
55
56</PRE>
57
58<!--endarticle-->
59 <HR>
60 <P><UL>
61 <!--threads-->
62 <LI>Previous message: <A HREF="000718.html">[IRCServices Coding] nick.db - Invalid Format
63</A></li>
64 <LI>Next message: <A HREF="000690.html">[IRCServices Coding] Re: Chanserv problem with .33?
65</A></li>
66 <LI> <B>Messages sorted by:</B>
67 <a href="date.html#719">[ date ]</a>
68 <a href="thread.html#719">[ thread ]</a>
69 <a href="subject.html#719">[ subject ]</a>
70 <a href="author.html#719">[ author ]</a>
71 </LI>
72 </UL>
73
74</body></html>