This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
Re[2]: 19990705 snapshot
- To: Chris Faylor <cgf@cygnus.com>
- Subject: Re[2]: 19990705 snapshot
- From: Egor Duda <deo@logos-m.ru>
- Date: Sat, 10 Jul 1999 20:10:34 +0400
- CC: cygwin-developers <cygwin-developers@sourceware.cygnus.com>
- Organization: DEO
- References: <19990708172005.A3884@cygnus.com>
- Reply-To: Egor Duda <deo@logos-m.ru>
Hi!
July, 9 1999 Chris Faylor cgf@cygnus.com wrote:
>>Another question: has the CYGWIN=strace=1,somefile functionality been
>>deprecated with the advent of the strace program?
CF> It hasn't been deprecated. It has been removed. You have to use
CF> the strace program.
I've got some problems with new strace mechanism too :( Issuing
command
strace -otrace.dump -f man man
leads to some strange results.
At least one thing that had to be added to strace.cc code is to make
it handle EVENT_EXCEPTION. Sometimes stracing "man man" just freezes
because /usr/local/bin/tbl (called by man) traps and starts to send
EXCEPTION event to strace process over and over again.
Would you consider making selection between new and old tracing scheme
to be an option at dll build time?
I've even built strace.exe under mingw, but results was the same. :(
Sometimes strace.exe just got killed by kernel (i've inserted debug
printf at the exit from main cycle at proc_child, but it didn't show
up), and groff, had been left alone and popped a dialog window that
noone can handle his breakpoint. Can it have something to do with
reparenting?
I'll attach one of strace logs.
Egor. mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19
trace.dump.gz