svadev AT lists.siebelschool.illinois.edu
Subject: Svadev mailing list
List archive
- From: Matthew Wala <wala1 AT illinois.edu>
- To: svadev AT cs.uiuc.edu
- Subject: [svadev] string transform and complete flag
- Date: Tue, 5 Apr 2011 20:56:25 -0500
- List-archive: <http://lists.cs.uiuc.edu/pipermail/svadev>
- List-id: <svadev.cs.uiuc.edu>
Hi everyone:
What's the purpose of the "complete" byte which is passed as an
argument and the end of the pool_* string
functions? In what I've done so far I haven't used it at all, I just
ignored it and it didn't seem to cause any
issues until now. However I realized that whenever I try to pass a
NULL pointer directly as an argument to a
string function that has runtime checks, sometimes I get the following
error, which happens during the computation
of the complete flag, and I don't think any of my changes are causing this:
sc: String.cpp:280: unsigned int
safecode::StringTransform::getDSFlags(const llvm::Value*, const
llvm::Function*): Assertion `DSN && "getDSFlags(): No DSNode for the
specified value!\n"' failed.
This is a problem because passing NULL pointers is legitimate for
certain functions that should have their own
runtime checks (eg., strtok). How do I fix this?
Matt
- [svadev] string transform and complete flag, Matthew Wala, 04/05/2011
- Re: [svadev] string transform and complete flag, John Criswell, 04/05/2011
- Re: [svadev] string transform and complete flag, Matthew Wala, 04/06/2011
- Re: [svadev] string transform and complete flag, John Criswell, 04/06/2011
- Re: [svadev] string transform and complete flag, Matthew Wala, 04/06/2011
- Re: [svadev] string transform and complete flag, John Criswell, 04/05/2011
Archive powered by MHonArc 2.6.16.