davide nailed it! OK, PTAL. You can now do stuff like strace /bin/date
and it works. I don't promise there are not potential issues, ha ha!, but this is going to be very handy. ron On Wed, Jan 27, 2016 at 7:10 AM 'Davide Libenzi' via Akaros < [email protected]> wrote: > Maybe you should not be closing the queue on proc_destroy(), otherwise > reads from parent will fail? > > CHILD: PARENT: > trace > trace > die/proc_destroy > read() -> queue closed even with data > in it > > > > On Wed, Jan 27, 2016 at 6:59 AM, Davide Libenzi <[email protected]> > wrote: > >> Oh, no, "p" is the target PID not the calling process. >> >> On Wed, Jan 27, 2016 at 6:56 AM, Davide Libenzi <[email protected]> >> wrote: >> >>> Maybe if you actually open the trace file before the fork? ☺ >>> >>> >>> On Tue, Jan 26, 2016 at 8:46 PM, ron minnich <[email protected]> wrote: >>> >>>> yeah, I agree with you. I walked the exec code and I'm not seeing it. >>>> Since I *think* exec uses the same proc struct I don't see where >>>> proc->strace is getting cleared. >>>> >>>> Anyway, a nice mystery for someone who wants to try to find it before >>>> me :-) >>>> >>>> ron >>>> >>>> On Tue, Jan 26, 2016 at 8:37 PM 'Davide Libenzi' via Akaros < >>>> [email protected]> wrote: >>>> >>>>> My off-source guess is that there might be a traceme flag in the >>>>> struct proc we are not cloning correctly at exec() time. >>>>> On Jan 26, 2016 20:13, "ron minnich" <[email protected]> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Tue, Jan 26, 2016 at 7:37 PM 'Davide Libenzi' via Akaros < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Oh, IC. >>>>>>> BTW, looking at syspipe(), it seems to have the >>>>>>> rely-on-values-written-after-waserror issue. >>>>>>> >>>>>>> >>>>>>> >>>>>> Thanks, I'll take a look :-) >>>>>> >>>>>> If you can, could you see if you can see what I'm missing on >>>>>> inheriting strace after exec? >>>>>> >>>>>> The issue is that >>>>>> strace /bin/date >>>>>> seems only to show the exec system call, and nothing more. I'm >>>>>> missing something! >>>>>> >>>>>> ron >>>>>> >>>>>> -- >>>>>> >>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Akaros" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected]. >>>>>> To post to this group, send email to [email protected]. >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Akaros" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To post to this group, send email to [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Akaros" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To post to this group, send email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >> > -- > You received this message because you are subscribed to the Google Groups > "Akaros" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Akaros" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
