On Sun, 3 Apr 2005, Craig White wrote:
(gdb) run -f Starting program: /usr/lib/cyrus-imapd/quota -f (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -1218568064 (LWP 7193)] (no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1218568064 (LWP 7193)] 0x00d1c513 in _int_realloc () from /lib/tls/libc.so.6
If you have one stack frame only, you have some serious problems. I doubt you do. What's the rest of the backtrace? (gdb's "where" commands)---- thanks - I know not of these things - appreciate your patience with me.
(gdb) where #0 0x00be1513 in _int_realloc () from /lib/tls/libc.so.6 #1 0x00be0156 in realloc () from /lib/tls/libc.so.6 #2 0x00c1b586 in glob_in_dir () from /lib/tls/libc.so.6 #3 0x00c1a7fc in glob () from /lib/tls/libc.so.6 #4 0x0808328e in mboxlist_findsub_alt () #5 0x0804baa0 in ?? () #6 0x0811b1e8 in ?? () #7 0xbfff8580 in ?? () #8 0x00000000 in ?? ()
indeed, it was not the only stack. There was no rest of the backtrace unless you are asking for the stuff that came 'before' I executed '(gdb) run -f' which I didn't include because I didn't think that it had meaningful information but for completeness...
no, you answered what i wanted to know, above. I need to look at the regex code in mboxlist_findsub_alt
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
