[lug] gdb & pthreads

[Ken Weinert]

ulimit -c unlimited

ulimit is probably set to 0 for core files since "normal" users don't
require them, know what they are, etc and they just eat up disk space
(sometimes a *lot* of disk space) if you just leave them around.

* Kevin King (kevin at precisonline.com) [000719 19:27]:
> I am compiling w/ -g, but I still do not get a core file.  Anything
> else come to mind?
> 
> (Caldera OL 2.2)
> 
> --Kevin
> kevin at precisonline.com
> http://www.precisonline.com
> http://www.precisonline.com/gold.htm
> 
> -----Original Message-----
> From: Rich Deeming <rdeeming at mcdata.com>
> To: lug at lug.boulder.co.us <lug at lug.boulder.co.us>
> Date: Wednesday, July 19, 2000 10:54 AM
> Subject: Re: [lug] gdb & pthreads
> 
> 
> >Compile with -g option.
> >Here is a link that I have found to be very useful.
> >http://www.pi.infn.it/ASISdoc/GNU.LANG/gdb-4.16/gdb_toc.html
> >
> >Rich
> >
> >Kevin King wrote:
> >
> >> For some reason I am not getting a core file.  Could you tell me
> how
> >> to enable this on Caldera 2.2?
> >>
> >> Thanks.
> >>
> >> --Kevin
> >> kevin at precisonline.com
> >> http://www.precisonline.com
> >> http://www.precisonline.com/gold.htm
> >>
> >> -----Original Message-----
> >> From: Rich Deeming <rdeeming at mcdata.com>
> >> To: lug at lug.boulder.co.us <lug at lug.boulder.co.us>
> >> Date: Wednesday, July 19, 2000 9:03 AM
> >> Subject: Re: [lug] gdb & pthreads
> >>
> >> >When the program seg faults are you generating a core file?
> >> >If so $gdb progname -c core should give you the location of
> >> >where the fault occurs.
> >> >
> >> >Rich
> >> >
> >> >Kevin King wrote:
> >> >
> >> >> I have created and am testing a multithreaded program which seg
> >> >> faults under load.  I'm trying to trace the fault using gdb,
> but
> >> gdb
> >> >> stops when the first subordinate thread terminates.  The main
> >> thread
> >> >> continues running (though it is effectively a zombie) and needs
> to
> >> be
> >> >> killed manually.
> >> >>
> >> >> This gdb was specifically downloaded from the Caldera site
> because
> >> it
> >> >> has pthreads support, but if I can't trace into the threads --
> or
> >> at
> >> >> least keep the debugger running after the first thread
> terminates,
> >> >> it's not of much use.  Does anyone happen to have any advice or
> >> ideas
> >> >> of options or something w/ gdb which will allow me to use it to
> >> trace
> >> >> this fault?  Or perhaps some other tool?  Or is there perhaps a
> >> >> compiler option to enable extended information on a fault?
> >> >>
> >> >> Thanks!
> >> >>
> >> >> --Kevin
> >> >> kevin at precisonline.com
> >> >> http://www.precisonline.com
> >> >> http://www.precisonline.com/gold.htm
> >> >>
> >> >> _______________________________________________
> >> >> Web Page:  http://lug.boulder.co.us
> >> >> Mailing List:
> http://lists.lug.boulder.co.us/mailman/listinfo/lug
> >> >
> >> >
> >> >
> >> >_______________________________________________
> >> >Web Page:  http://lug.boulder.co.us
> >> >Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> >> >
> >> >
> >>
> >> _______________________________________________
> >> Web Page:  http://lug.boulder.co.us
> >> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> >
> >
> >
> >_______________________________________________
> >Web Page:  http://lug.boulder.co.us
> >Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> >
> >
> 
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> 

-- 
Ken Weinert   kenw at ihs.com 303-858-6956 (V) 978-336-5652 (F)
PGP: DF 2B 6C 72 33 BE 06 D1  9D C4 ED 32 36 97 C0 6E
I hit the CTRL key but I'm still not in control!