Date: Wed, 22 Nov 2006 16:13:52 -0800 From: "Kip Macy" <kip.macy@gmail.com> To: "David Xu" <davidxu@freebsd.org> Cc: freebsd-threads@freebsd.org Subject: Re: gcore thread problem? Message-ID: <b1fa29170611221613o66fd645ct92e3ca37af42aa67@mail.gmail.com> In-Reply-To: <200611230801.45966.davidxu@freebsd.org> References: <90242b1f0611220412l4ef4c92jd6f3e308f7c882fd@mail.gmail.com> <200611230801.45966.davidxu@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
That isn't how multi-threading is handled for core-files. For each thread an additional set of GPRs and FPRs is added to the elf header. -Kip On 11/22/06, David Xu <davidxu@freebsd.org> wrote: > > On Wednesday 22 November 2006 20:12, Vaidehi Shukla wrote: > > Hi All, > > > > 'gcore' doesn't display correct backtrace (info threads) for > multi-threaded > > application. Is there any way to get correct backtrace (i.e. info > threads) > > with gcore in freebsd?. Let me know if you can suggest some method to > get > > correct backtrace. > > > > Thanks & Regards, > > Vaidehi > > I think it becauses threaded application does not work correctly with > procfs, one problem is gcore is using files in /proc to get information, > if an application has thousands of thread, should kernel create so much > vnode for the application ? it seems to be overkill. > > David Xu > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b1fa29170611221613o66fd645ct92e3ca37af42aa67>