On Mon, Sep 30, 2013 at 09:51:02AM -0700, Ildar Muslukhov wrote: > On Fri, Sep 27, 2013 at 2:49 PM, Dave Jones <[email protected]> wrote: > > On Fri, Sep 13, 2013 at 12:53:16PM -0700, Ildar Muslukhov wrote: > > > This patch explicit selection of 32 or 64 bit version of a syscall via > > > parameter. > > > > I only just noticed this.. > > > > > - fprintf(stderr, " -c#: target specific syscall (takes syscall name as > > parameter).\n"); > > > + fprintf(stderr, " -c#,@: target specific syscall (takes syscall name > > as parameter and @ as architecture. No @ defaults to both archs.).\n"); > > > > The patch I ended up applying looks like it doesn't touch -c parsing. > > Is this incomplete ? > > Nope, > > The splitting of the parameter is done in the toggle_syscall function.
Ok, then I'm confused, because the syntax above doesn't seem to parse architecture. $ ./trinity -c open,x86_64 Trinity v1.3pre Dave Jones <[email protected]> No idea what architecture for syscall (open,x86_64) is Dave -- To unsubscribe from this list: send the line "unsubscribe trinity" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
