|
From: Eyal L. <ey...@ey...> - 2005-01-15 09:59:30
|
Jeremy Fitzhardinge wrote:
> On Sat, 2005-01-15 at 19:17 +1100, Eyal Lebedinsky wrote:
>
>>--2005-01-15 18:51:19.459 15031-- disInstr: unhandled instruction bytes: 0xF4 0xEB 0xDE 0xC7
>>--2005-01-15 18:51:19.459 15031-- at 0x1BEB1E23: abort (in /lib/tls/libc-2.3.2.so)
>>
>>vg built off latest cvs, on Debian testing.
>>
>>$ gcc --version
>>gcc (GCC) 3.3.5 (Debian 1:3.3.5-5)
>>Copyright (C) 2003 Free Software Foundation, Inc.
>>This is free software; see the source for copying conditions. There is NO
>>warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
>
> This looks like
> hlt
> jmp -34
>
> Hm, and since it's in abort(), perhaps its deliberately doing it to kill
> itself.
>
> Hm, but it does suggest it failed to kill itself with SIGABRT first.
>
> What does running with --trace-syscalls=yes or --trace-signals=yes say?
Running as follows, log attached.
valgrind --tool=memcheck \
--leak-check=yes \
--show-reachable=no \
--num-callers=32 \
--error-limit=no \
--run-libc-freeres=no \
--trace-syscalls=yes \
The executable is a server. When launched if immediately forks itself
and the parent only takes care of restarting the child if it dies. It
seems as if the child died just after launch and the parents exited
clean.
Naturally, there are a number of threads running even when the server
is idle. For example, my main() is actually a thread, the real main
that crt calls is practically empty, doing just a thread_create and
_join.
I should say that I avoided using cvs for a few months now since I
had problems spawning processes (I follow branch 2.2.0). I decided
to give head a try after reading of the progress done in the
threading area.
--
Eyal Lebedinsky (ey...@ey...) <http://samba.org/eyal/>
If attaching .zip rename to .dat
|