Hey everyone,
I was trying to work out how exactly klee handles symbolic files.
So i looked into the definition of the __fd_open() call stub, in
runtime/POSIX/fd.c
This is what I could make out:

The code tries to retrieve an unused file descriptor by scanning linearly.
Then if a fd is found, it tries to see if the pathname provided in the
argument actually exists. if so, it opens the system file and returns back.
If not, then it tries to create a symbolic file.
It does this by calling :
syscall(__NR_open, __concretize_string(pathname), flags, mode);

This call is failing. I am guessing that the reason for that is
__concretize_string() is producing strings which cannot be valid filenames.
I simply printfed this value. I am unable to find the definition of
__concretize_string. Can anyone help me? Also, am I missing out something?
Should I be doing something different to create symbolic files?

-Lokesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://keeda.Stanford.EDU/pipermail/klee-dev/attachments/20100207/a22eb96a/attachment.html
 

Reply via email to