Firefox, Thunderbird, and GIMP having problems with clang

[Jukka A. Ukkonen]

Howdy,

This is just in case nobody has noticed yet.
When I built the FreeBSD-9.1 kernel and user space on AMD64 using clang
all of Firefox, Thunderbird, and GIMP began terminating unexpectedly soon
after they had been started. They just quickly flashed a window on the
display and disappeared again. I did not even try to tracing GIMP, but
both firefox and thunderbird showed symptoms like those below...
(These were collected from firefox using ktrace and kdump.)

 71185 firefox  CALL  clock_gettime(0x4,0x7fffffff2108)
 71185 firefox  RET   clock_gettime 0
 71185 firefox  CALL  clock_gettime(0x4,0x7fffffff2108)
 71185 firefox  RET   clock_gettime 0
 71185 Proxy Resolution RET   wait4 35839/0x8bff
 71185 firefox  CALL  clock_gettime(0x4,0x7fffffff2108)
 71185 firefox  RET   clock_gettime 0
 71185 firefox  CALL  clock_gettime(0x4,0x7fffffff2108)
 71185 firefox  RET   clock_gettime 0
 71185 firefox  CALL  clock_gettime(0x4,0x7fffffff2108)
 71185 firefox  RET   clock_gettime 0
 71185 firefox  CALL  clock_gettime(0x4,0x7fffffff2108)
 71185 firefox  RET   clock_gettime 0
 71185 firefox  CALL  clock_gettime(0x4,0x7fffffff2108)
 71185 firefox  RET   clock_gettime 0
 71185 Proxy Resolution CALL  exit(0)
 71185 firefox  CALL  clock_gettime(0x4,0x7fffffff2108)
 71185 firefox  RET   _umtx_op -1 errno 4 Interrupted system call
 71185 mozStorage #2 RET   _umtx_op -1 errno 4 Interrupted system call
 71185 firefox  RET   _umtx_op -1 errno 4 Interrupted system call
 71185 Gecko_IOThread GIO   fd 18 wrote 32 bytes
       0x0000 1300 0000 0000 0000 ffff 0100 0000 0000  |................|
       0x0010 0000 0000 0000 0000 0303 0300 0000 0000  |................|
 71185 HTML5 Parser RET   _umtx_op -1 errno 4 Interrupted system call
 71185 firefox  RET   poll -1 errno 4 Interrupted system call
 71185 mozStorage #1 RET   _umtx_op -1 errno 4 Interrupted system call
 71185 Cert Verify RET   _umtx_op -1 errno 4 Interrupted system call
 71185 Gecko_IOThread RET   kevent -1 errno 4 Interrupted system call
 71185 Socket Thread RET   poll -1 errno 4 Interrupted system call
 71185 DOM Worker RET   _umtx_op -1 errno 4 Interrupted system call
 71185 mozStorage #4 RET   _umtx_op -1 errno 4 Interrupted system call
 71185 mozStorage #3 RET   _umtx_op -1 errno 4 Interrupted system call
 71185 Cache I/O RET   _umtx_op -1 errno 4 Interrupted system call
 71185 XPCOM CC RET   _umtx_op -1 errno 4 Interrupted system call
 71185 Timer    RET   _umtx_op -1 errno 4 Interrupted system call
 71185 StreamTrans #46 RET   _umtx_op -1 errno 4 Interrupted system call
 71185 firefox  RET   clock_gettime 0
 71185 Hang Monitor RET   _umtx_op -1 errno 4 Interrupted system call
 71185 JS GC Helper RET   _umtx_op -1 errno 4 Interrupted system call
 71185 JS Watchdog RET   _umtx_op -1 errno 4 Interrupted system call

This was right at the end of the ktrace/kdump trace log. So, there
was nothing more after those lines.

I really have no idea yet about what this might be indicating.
This is just FYI in case someone else might be able to reproduce
the symptoms I have seen.

I hope this helps.


	Cheers,
		// jau
.---  ..-  -.-  -.-  .-    .-  .-.-.-    ..-  -.-  -.-  ---  -.  .  -.
  /    Jukka A. Ukkonen,                             Oxit Ltd, Finland
 /__   M.Sc. (sw-eng & cs)                    (Phone) +358-500-606-671
   /   Internet: Jukka.Ukkonen(a)Oxit.Fi
  /    Internet: jau(a)iki.fi
 v
        .---  .-  ..-  ...-.-  ..  -.-  ..  .-.-.-  ..-.  ..
+ + + + My opinions are mine and mine alone, not my employers. + + + +