Re: [Valgrind-users] unhandled instruction bytes

[folkert <fo...@va...>]

> > The 2 calls it does are:
> > 
> > print_char:
> >      movb (%esi), %al
> >      movb %al, buffer
> >      movl $4, %eax
> >      movl $1, %ebx
> >      movl $buffer, %ecx
> >      movl $1, %edx
> >      int  $0x80
> >      ret
> > 
> > exit:
> >      movl $1, %eax
> >      movl $0, %ebx
> >      int  $0x80
> 
> Valgrind can't run just any executable binary. It has quite a lot of hard
> coded limitations that correspont (mostly) to what compilers and link
> editors will produce. So if you use assembler and use opcodes not normally
> generated by compilers then it won't work.
...
> So int 0x80 results in a decode error.
> 
> Can you use syscall?

That solves the problem.
Thanks!