|
Message-ID: <CACsECNd+C1jvfke4FDVY8wJ6w8hf_m_t8efsS=pzGOkqx4r1XA@mail.gmail.com>
Date: Wed, 14 Oct 2015 12:21:05 +0200
From: Alex <alexinbeijing@...il.com>
To: musl@...ts.openwall.com
Subject: Re: [PATCHv3 1/3] fix matching errors for overwritten
registers in x86 CFI generation script
On Wed, Oct 14, 2015 at 12:42 AM, Rich Felker <dalias@...c.org> wrote:
> On Tue, Oct 13, 2015 at 01:28:50PM +0200, Alex Dowad wrote:
> > Here is the latest iteration. I have merged 2 previously separate
> commits, and
> > fixed up the matching of registers (for the purpose of identifying
> overwritten
> > registers).
> >
> > As usual, thanks for the feedback. AD
>
> Thanks! I'm committing them all now. I'm sorry for not catching this
> before -- I realized that the index register thing was also an
> existing bug in mov handling, not just a new bug added in the operand
> order patch, so I split it out into a separate commit. I did basic
> regression testing on i386 (making sure gdb backtrace from syscalls
> still works) and tested that the x86_64 also seems to work (it does).
Thanks!
This has been an interesting exercise so far. Is there any other arch which
you think it would be worthwhile to develop a CFI generation script for? It
should be something which has enough users to avoid problems with bitrot.
AD
Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.