我如何使用xdebug跟踪我的卷曲(How can I track my curl with xdebug)

 那么，你可以尝试： 
 
#define system DontEvenThinkAboutUsingThisFunction
#define exec   OrThisOneYouClown
 
 在一个头文件中，但我非常确定任何值得他们的盐的代码猴可以绕过这样的“保护”。 
 
 我有兴趣了解为什么你认为这是必要的（如果我们更好地理解问题，可能会有更好的解决方案）。 
 
 唯一想到的是，你想提供一些类似于Euler项目的在线编译器/ runner。 如果是这样的话，那么你可以搜索字符串system<whitespace>(的代码system<whitespace>(作为一个选项，但即使如此，一个确定的派对可能只是： 
 
#define InoccuousFunction system
 
 绕过你的防御。 
 
 如果是这样的话，你可能要考虑使用类似chroot东西，这样任何人都无法访问任何危险的二进制文件，如shutdown （并且该特定的野兽不应该由普通用户真正运行） - 在换句话说，限制他们的环境，使他们唯一可以看到的东西是gcc和它的亲属。 
 
 你需要做适当的沙盒，因为即使你以某种方式阻止他们运行外部程序，他们仍然可以做一些危险的事情，比如overwite文件或者打开套接字连接到他们自己的盒子，通过你的珍贵信息的内容发送。 

Well, you could try:
 
#define system DontEvenThinkAboutUsingThisFunction
#define exec   OrThisOneYouClown
 
in a header file but I'm pretty certain any code monkey worth their salt could bypass such a "protection".
 
I'd be interested in understanding why you thought this was necessary (there may be a better solution if we understood the problem better).
 
The only thing that comes to mind is that you want to provide some online compiler/runner akin to the Euler project. If that was the case, then you could search the code for the string system<whitespace>( as an option but, even then, a determined party could just:
 
#define InoccuousFunction system
 
to get around your defenses.
 
If that is the case, you might want to think about using something like chroot so that no-one can even get access to any dangerous binaries like shutdown (and that particular beast shouldn't really be runnable by a regular user anyway) - in other words, restrict their environment so that the only things they can even see are gcc and its kin.
 
You need to do proper sandboxing since, even if you somehow prevented them from running external programs, they may still be able to do dangerous things like overwite files or open up socket connections to their own box to send through the contents of your precious information.