Re: Re: time seg fault

[rjustinwilliams]

That makes sense. I was seeing a gentoo bug report that might indicate  
issues with hardened kernel (and/or version issue) and glibc's  
gettimeofday() function. That was filed for a different issue, but, found  
it interesting...
On Jul 23, 2009 2:22pm, Greg Wooledge <wooledg@eeg.ccf.org> wrote:
> On Thu, Jul 23, 2009 at 01:42:15PM -0400, Justin Williams wrote:

> > Greg, you mentioned that it might be a build bug causing headaches.

> > As the same build environment was used to build tcsh, and to

> > (re)build/upgrade bash on this system, and tcsh's time works while  
> bash's

> > doesn, I'm curious where the idea comes from. I don't doubt it, but I'm

> > curious what leads you to that.



> Well, my initial diagnosis of "a problem with the build" is very general.

> I just mean that the bash binary executable program is not a correct

> compilation of the source code, either because of a compiler bug, or

> any other really bizarre problem.



> Then you showed this:



> > >> > Attaching to program: /bin/bash, process 5647

> > >> > linux-nat.c:988: internal-error: linux_nat_attach: Assertion `pid  
> ==

> > >> GET_PID

> > >> > (inferior_ptid) && WIFSTOPPED (status) && WSTOPSIG (status) ==  
> SIGSTOP'

> > >> > failed.

> > >> > A problem internal to GDB has been detected,

> > >> > further debugging may prove unreliable.



> To which I responded:



> > >> Maybe your libc is broken? Or your compiler, if all of these are

> > >> self-compiled gentoo e-builds?



> If both bash and gdb are showing unexplained problems, then I would

> start looking at deeper levels for the problems -- C compiler, C library,

> kernel, hardware.