Re: [DynInst_API:] Rewriter output file naming question

[Andrew Bernat <bernat@xxxxxxxxxxx>]

The way we're using it. 

libelf internally maps a file into memory with mmap in shared mode; this means that changes to the file are apparent to libelf. When we start modifying the file to write a new one, that ... well, it screws everything up. 

Drew

On Nov 29, 2012, at 4:50 PM, Josh Stone <jistone@xxxxxxxxxx> wrote:

On 11/29/2012 02:20 PM, Andrew Bernat wrote:

We just ran into a problem where rewriting a file using the same name as
input and output will crash in libelf. We're going to add a check to
prevent this from crashing; is anyone currently relying on the ability
to rewrite a file in place.

I, for one, am not using rewriting at all.

But is this a problem in libelf itself, or just the way you're using it?
And if it's the library, which one are we talking about?  If it's
elfutils', then a report to elfutils-devel@xxxxxxxxxxxxxxxxxxxxxx would
be appreciated.

Thanks,
Josh

_______________________________________________
Dyninst-api mailing list
Dyninst-api@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api

--

Andrew Bernat

Paradyn Project

bernat@xxxxxxxxxxx

http://www.cs.wisc.edu/~bernat