Date: Thu, 6 Oct 2005 23:00:23 GMT From: Daniel Eischen <deischen@freebsd.org> To: freebsd-threads@FreeBSD.org Subject: Re: threads/84778: libpthread busy loop/hang with Java when handling signals and Runtime.exec Message-ID: <200510062300.j96N0NXL042263@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR threads/84778; it has been noted by GNATS. From: Daniel Eischen <deischen@freebsd.org> To: freebsd@spatula.net Cc: bug-followup@freebsd.org Subject: Re: threads/84778: libpthread busy loop/hang with Java when handling signals and Runtime.exec Date: Thu, 6 Oct 2005 18:59:14 -0400 (EDT) On Thu, 6 Oct 2005 freebsd@spatula.net wrote: > select, however, does call nanosleep, and nanosleep does call > _nanosleep... but you're right that everything after that looks broken... > though I've never seen a stack get smashed like that before. Usually I've > seen freakish addresses and "??" for function names, not addresses that > look reasonable and function names with symbols that can be actually > located. > > What happens when you gcore a running threaded process? Do the process's > threads stop while the core dump is being written? If not, could the > stack have changed while the core was being dumped and we're actually > seeing bits of stack from multiple running threads (and therefore > basically useless information)? I have no idea what or how gcore works. > Which thread do you see in a core dump if there are multiple threads? I don't know. I've only ever used gdb on running processes. -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200510062300.j96N0NXL042263>