[leafnode-list] ma9rc1 and dmalloc

[Mike Castle <dalgoda@xxxxxxxxxxxxx>]

Hmmm... I'm using dmalloc_verify() all over the place to try to track down
some issues.

One thing I just noticed is:

(gdb) bt
#0  dmalloc_verify (pnt=0x0) at dmalloc_lp.c:613
#1  0x0804b10d in main (argc=2, argv=0xbffffd24)
    at ../leafnode-2.0b8_ma9rc1/fetchnews.c:1709
#2  0x08061195 in __libc_start_main (main=0x804a940 <main>, argc=2,
    ubp_av=0xbffffd24, init=0x80480b4 <_init>, fini=0x80a6f60 <_fini>,
    rtld_fini=0, stack_end=0xbffffd1c) at
./sysdeps/generic/libc-start.c:129
(gdb) up
#1  0x0804b10d in main (argc=2, argv=0xbffffd24)
    at ../leafnode-2.0b8_ma9rc1/fetchnews.c:1709
1709    dmalloc_verify(0);
(gdb) list
1704        else if (setjmp(jmpbuffer) != 0) {
1705            servers = NULL;         /* in this case, jump the while ...
loop */
1706        }
1707
1708        while (servers) {
1709    dmalloc_verify(0);
1710            current_server = servers;
1711            if (forceactive) {
1712                (void)dirtyactive(current_server);
1713            }


This is pretty early in the game.  But it only happened when I had a left
over file in in.coming.

[This is more of a note to self to track this down after finding the other
one.]

mrc [being very unproductive at work today]
-- 
     Mike Castle      dalgoda@xxxxxxxxxxxxx      www.netcom.com/~dalgoda/
    We are all of us living in the shadow of Manhattan.  -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc

-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list