From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shaw Terwilliger To: Nicolas Vignal Cc: gdb@sources.redhat.com Subject: Re: thread exit goes defunct Date: Mon, 12 Feb 2001 08:51:00 -0000 Message-id: <20010212105114.B26819@lister.sourcegear.com> References: <01021216193600.01165@nicolas> X-SW-Source: 2001-02/msg00123.html Nicolas Vignal wrote: > Under gdb when a thread exit, he goes in the defunct state. I've been wondering about this too. Since the old threads don't die, I quickly run out of processes, which makes debugging long-running servers (which spawn new threads on new connections) difficult. -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqIFIIACgkQPEbgvbl6u4HH3gCgiXrPn/gg4AbhpH0SKa2K3ful tGQAn0u2sRKBx4lCwnnLeGlUBMM/bAah =qBve -----END PGP SIGNATURE----- >From nsd@redhat.com Mon Feb 12 09:46:00 2001 From: Nick Duffek To: eliz@is.elta.co.il Cc: gdb@sources.redhat.com, kettenis@wins.uva.nl Subject: Re: Register cache Date: Mon, 12 Feb 2001 09:46:00 -0000 Message-id: <200102121753.f1CHr9t11723@rtl.cygnus.com> References: X-SW-Source: 2001-02/msg00124.html Content-length: 1377 On 12-Feb-2001, Eli Zaretskii wrote: >So you are telling, in effect, that it's okay to have >i387_supply_fsave get all the FP registers Yes, I think that's a reasonable and useful i387 interface. >and x86 targets which don't like that should provide ther own code >instead of using i387_supply_fsave? Certainly they can't use i387_supply_fsave, so something like i387_supply_fpreg would be necessary. Note that the {supply,fill}_*regset functions aren't part of the register cache interface: they're just a set of target-specific functions that several targets happen have in common. Those targets generally can't fetch just one floating-point register, which is why the supply_*regset functions lack a REGNO argument. As Mark said, the register cache continues to work properly if target_fetch_registers fetches more registers than requested, so there's no loss and potentially some gain for those targets to fetch all fp registers. If it's possible and more efficient on your target to fetch one fp register instead of all of them, then I think i387_supply_fpreg is a good idea. In my opinion, interface expansion is preferable to code duplication, so I agree with your patch to put i387_supply_fpreg in i387-nat.c. However, that's really a coding philosophy issue, and since Mark wrote i387-nat.c, I'm inclined to bow to his opinion on how it gets changed. Nick