From ocelaiwo at gmail.com Thu Nov 3 14:28:53 2022 From: ocelaiwo at gmail.com (Alex Babushkin) Date: Thu, 3 Nov 2022 17:28:53 +0300 Subject: [klee-dev] On how the standard library is linked. Message-ID: Hello. KLEE can call functions that do not have IR available as externals. Some C standard library functions are also called as externals (e.g. printf). How is the standard library linked to the JIT engine that calls externals? Also, why isn't loading of binary-only libraries supported in KLEE? Are there serious reasons for that or is it just considered unnecessary? Best regards, Alex. -------------- next part -------------- HTML attachment scrubbed and removed From c.cadar at imperial.ac.uk Sat Nov 5 22:52:55 2022 From: c.cadar at imperial.ac.uk (Cristian Cadar) Date: Sat, 5 Nov 2022 22:52:55 +0000 Subject: [klee-dev] On how the standard library is linked. In-Reply-To: References: Message-ID: Hi Alex, We typically link against a custom version of uclibc, where printf is treated specially by default as an external function. Does this answer your question? It is possible to load binary-only libraries with KLEE via the --load option. Best, Cristian On 03/11/2022 14:28, Alex Babushkin wrote: > Hello. > > KLEE can call functions that do not have IR available as externals. Some > C standard library functions are also called as externals (e.g. printf). > How is the standard library linked to the JIT engine that calls > externals?? Also, why isn't loading of binary-only libraries supported > in KLEE? Are there serious reasons for that or is it just considered > unnecessary? > > Best regards, > Alex. > > _______________________________________________ > klee-dev mailing list > klee-dev at imperial.ac.uk > https://mailman.ic.ac.uk/mailman/listinfo/klee-dev