ss> I am trying to setup a very basic system for just tracing the sqlite code, ss> but I didn't have any luck.
ss> Code::Blocks compiles everything, but when it comes to tracing, it traces ss> even through comments. ss> Eclipse CDT includes the sqlite3.h, and accepts the *sqlite3 pointer, but ss> doesn't accept the function db_open. Actually i don't understand how this is ss> possible. ss> DevC++ doesn't compile sqlite3 and signals lots of errors in sqlite3.c. ss> The environments are setup for c++ compiling via mingw and run the ss> traditional hello world, and the sqlite used is the amalgamation. ss> Is there a straightforward way to trace sqlite, without messing around?? ss> Thanks, ss> Saverio >What do you mean by tracing. Do you mean code profiling? Or easy >navigation though the code? Or ...? Just step-in; I'm studying the sqlite code and it would be easier if I could see the internal in action. Thank you! Saverio -- View this message in context: http://www.nabble.com/Basic-system-setup-for-tracing--tp15963983p15971082.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
