Hi Mehdi,
Note that the main() function becomes __user_main() when you link with
uClibc, so the missing info regarding main() is expected. If you find
problems with the actual user code that you compile, you can open an
issue at https://github.com/klee/klee/issues
Best,
Cristian
On 03/12/2025 06:36, Mehdi Honarvar wrote:
Hi there,
I was following the instructions in the link below and encountered an issue:
https://klee-se.org/tutorials/testing-coreutils/
<https://klee-se.org/tutorials/testing-coreutils/>
I ran the following configuration and commands:
`CC=wllvm ../configure --program-suffix=-6.11 --disable-nls \ CFLAGS="-g
-O0 -Xclang -disable-llvm-passes -D__NO_STRING_INLINES \
-D_FORTIFY_SOURCE=0 -U__OPTIMIZE__" make -j
cd src
ls -l ls echo
cat ./cat --version
find . -executable -type f | xargs -I '{}' extract-bc -l
/usr/lib/llvm-16/bin/llvm-link '{}'
ls -l ls.bc
klee --libc=uclibc --posix-runtime ./echo.bc --sym-arg 3
kcachegrind klee-last/run.istats
(also tried build klee with llvm-13 and llvm-16)
My issue is that in kcachegrind, under the Source Code view, some
functions show proper source information like uClibc_main, but others —
such as `main` — do not.
How can I fix this problem or ensure that all functions include source
mappings?(see attachment)
Best regards,
Mehdi H.
_______________________________________________
klee-dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
klee-dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
