Re: [sqlite] Basic system setup for tracing?
Tuesday, March 11, 2008, 11:10:03 AM, you wrote: ss>> I am trying to setup a very basic system for just tracing the sqlite ss> code, ss>> but I didn't have any luck. ss>> Code::Blocks compiles everything, but when it comes to tracing, it ss> traces ss>> even through comments. ss>> Eclipse CDT includes the sqlite3.h, and accepts the *sqlite3 pointer, ss> but ss>> doesn't accept the function db_open. Actually i don't understand how ss> 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 ...? ss> Just step-in; I'm studying the sqlite code and it would be easier if I could ss> see the internal in action. I can't comment on the compilers you mention, however Microsoft VC6 has no problem tracing through the SQLite code in the debugger. -- Best regards, Neville Franks, http://www.surfulater.com http://blog.surfulater.com ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Basic system setup for tracing?
"software.simian" <[EMAIL PROTECTED]> wrote: > > Just step-in; I'm studying the sqlite code and it would be easier if I could > see the internal in action. > * Compile with -DSQLITE_DEBUG=1 * PRAGMA vdbe_trace=ON; * PRAGMA vdbe_listing=ON; -- D. Richard Hipp <[EMAIL PROTECTED]> ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Basic system setup for tracing?
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
Re: [sqlite] Basic system setup for tracing?
Tuesday, March 11, 2008, 9:42:37 AM, you wrote: 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 ...? -- Best regards, Neville Franks, http://www.surfulater.com http://blog.surfulater.com ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] Basic system setup for tracing?
I am trying to setup a very basic system for just tracing the sqlite code, but I didn't have any luck. Code::Blocks compiles everything, but when it comes to tracing, it traces even through comments. Eclipse CDT includes the sqlite3.h, and accepts the *sqlite3 pointer, but doesn't accept the function db_open. Actually i don't understand how this is possible. DevC++ doesn't compile sqlite3 and signals lots of errors in sqlite3.c. The environments are setup for c++ compiling via mingw and run the traditional hello world, and the sqlite used is the amalgamation. Is there a straightforward way to trace sqlite, without messing around?? Thanks, Saverio -- View this message in context: http://www.nabble.com/Basic-system-setup-for-tracing--tp15963983p15963983.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
