Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 9 Feb 2012 17:53:55 -0800
From:      Dmitry Mikulin <dmitrym@juniper.net>
To:        Konstantin Belousov <kostikbel@gmail.com>
Cc:        freebsd-current Current <freebsd-current@freebsd.org>, Marcel Moolenaar <marcelm@juniper.net>
Subject:   Re: [ptrace] please review follow fork/exec changes
Message-ID:  <4F3478B3.9040809@juniper.net>
In-Reply-To: <20120210001725.GJ3283@deviant.kiev.zoral.com.ua>
References:  <20120130192727.GZ2726@deviant.kiev.zoral.com.ua> <4F2C756A.80900@juniper.net> <20120204204218.GC3283@deviant.kiev.zoral.com.ua> <4F3043E2.6090607@juniper.net> <20120207121022.GC3283@deviant.kiev.zoral.com.ua> <4F318D74.9030506@juniper.net> <4F31C89C.7010705@juniper.net> <4F3318AD.6000607@juniper.net> <20120209122908.GD3283@deviant.kiev.zoral.com.ua> <4F34311A.9050702@juniper.net> <20120210001725.GJ3283@deviant.kiev.zoral.com.ua>

next in thread | previous in thread | raw e-mail | index | archive | help


On 02/09/2012 04:17 PM, Konstantin Belousov wrote:
> On Thu, Feb 09, 2012 at 12:48:26PM -0800, Dmitry Mikulin wrote:
>>> The semantic of PL_FLAG_EXEC up until now is very simple: it indicates
>>> that current stop occured during the first return to usermode after
>>> successful exec. The proposed patch breaks the semantic, because now
>>> some stops which satisfy the stated condition are no longer marked with
>>> the flag.
>>>
>>> That said, I am lost. You stated that you still need some stops at
>>> exec even when not PT_FOLLOW_EXEC is requested. Why usermode cannot
>>> remember whether the PT_FOLLOW_EXEC was set for the process, and ignore
>>> PL_FLAG_EXEC if not requested ?
>> I was trying to avoid making ugly changes in gdb if it was possible not to
>> make ugly changes in the kernel. I changed gdb to work without
>> PT_FOLLOW_EXEC.
> So, does the patch below helps you, or did I missed something again ?

It works, but I managed to make gdb work without it. So, PT_FOLLOW_EXEC is not needed now.
Sorry for the confusion.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F3478B3.9040809>