Re: ctfmerge core dump

2012-05-31 Thread John Baldwin
On Thursday, May 24, 2012 4:10:59 pm Sergey Dyatko wrote: > 2012/5/7 Steve Wills > > > > On 2012/5/6 5:08, b. f. wrote: > > >> On 5/5/12, Steve Wills wrote: > > >>> Thanks for the info. I took a look at the dump and see this: > > >>> > > >>> % sudo gdb /usr/bin/ctfmerge ctfmerge.core > > >>> [GD

Re: ctfmerge core dump

2012-05-24 Thread Sergey Dyatko
2012/5/7 Steve Wills > > On 2012/5/6 5:08, b. f. wrote: > >> On 5/5/12, Steve Wills wrote: > >>> Thanks for the info. I took a look at the dump and see this: > >>> > >>> % sudo gdb /usr/bin/ctfmerge ctfmerge.core > >>> [GDB will not be able to debug user-mode threads: Undefined symbol > >>> "td_

Re: ctfmerge core dump

2012-05-07 Thread Steve Wills
> On 2012/5/6 5:08, b. f. wrote: >> On 5/5/12, Steve Wills wrote: >>> Thanks for the info. I took a look at the dump and see this: >>> >>> % sudo gdb /usr/bin/ctfmerge ctfmerge.core >>> [GDB will not be able to debug user-mode threads: Undefined symbol >>> "td_thr_getxmmregs"] > > Hmm, is the thre

Re: ctfmerge core dump

2012-05-06 Thread David Xu
On 2012/5/6 5:08, b. f. wrote: On 5/5/12, Steve Wills wrote: On 05/05/12 15:43, b. f. wrote: Steve Wills wrote: After updating from -CURRENT as of April 5 to one built today, I now get a core dump running ctfmerge on libc: ctfmerge -L VERSION -g -o libc.so.7 syscall.So fork.So.. Bus erro

Re: ctfmerge core dump

2012-05-06 Thread Outback Dingo
On Sat, May 5, 2012 at 8:26 PM, Outback Dingo wrote: > On Sat, May 5, 2012 at 7:54 PM, David Xu wrote: >> On 2012/5/6 5:08, b. f. wrote: >>> >>> On 5/5/12, Steve Wills  wrote: On 05/05/12 15:43, b. f. wrote: > > Steve Wills wrote: >> >> After updating from -CURRENT as of

Re: ctfmerge core dump

2012-05-05 Thread Outback Dingo
On Sat, May 5, 2012 at 7:54 PM, David Xu wrote: > On 2012/5/6 5:08, b. f. wrote: >> >> On 5/5/12, Steve Wills  wrote: >>> >>> On 05/05/12 15:43, b. f. wrote: Steve Wills wrote: > > After updating from -CURRENT as of April 5 to one built today, I now > get > a core dump ru

Re: ctfmerge core dump

2012-05-05 Thread David Xu
On 2012/5/6 5:08, b. f. wrote: On 5/5/12, Steve Wills wrote: On 05/05/12 15:43, b. f. wrote: Steve Wills wrote: After updating from -CURRENT as of April 5 to one built today, I now get a core dump running ctfmerge on libc: ctfmerge -L VERSION -g -o libc.so.7 syscall.So fork.So.. Bus erro

Re: ctfmerge core dump

2012-05-05 Thread b. f.
On 5/5/12, Steve Wills wrote: > On 05/05/12 15:43, b. f. wrote: >> Steve Wills wrote: >>> After updating from -CURRENT as of April 5 to one built today, I now get >>> a core dump running ctfmerge on libc: >>> >>> ctfmerge -L VERSION -g -o libc.so.7 syscall.So fork.So.. >>> Bus error (core dump

Re: ctfmerge core dump

2012-05-05 Thread Steve Wills
On 05/05/12 15:43, b. f. wrote: > Steve Wills wrote: >> After updating from -CURRENT as of April 5 to one built today, I now get >> a core dump running ctfmerge on libc: >> >> ctfmerge -L VERSION -g -o libc.so.7 syscall.So fork.So.. >> Bus error (core dumped) >> *** [libc.so.7] Error code 138 >

Re: ctfmerge core dump

2012-05-05 Thread b. f.
Steve Wills wrote: > After updating from -CURRENT as of April 5 to one built today, I now get > a core dump running ctfmerge on libc: > > ctfmerge -L VERSION -g -o libc.so.7 syscall.So fork.So.. > Bus error (core dumped) > *** [libc.so.7] Error code 138 > > Anyone else seeing this or have any i