When I say "path ... completely irrelevant" it means path doesn't cause the error and it doesn't matter at all what path you're giving - you can pass an empty path and the error will still persist.
ddd or gdb or whatever debugger you use - it doesn't show you memory access errors in your program (I heard totalview can do something like that but I didn't try that). But if you run your program under valgrind it will show you those types of errors. So go ahead and do it. Pavel On Tue, Oct 20, 2009 at 4:18 PM, Kavita Raghunathan <kavita.raghunat...@skyfiber.com> wrote: > I'm using ddd, its the GUI version of gdb. > > Are you saying that the file pathname is wrong ? When you say > "path give to sqlite.... is completely irrelevant" do you mean "db_filename"? > I printed this path out using the debugger and it looks correct. > > And you are correct, it does die in sqlite3_initialize while trying to free > the mutex pointer but the allocation of the pointer succeeds. So still lost. > > ----- Original Message ----- > From: "Pavel Ivanov" <paiva...@gmail.com> > To: "General Discussion of SQLite Database" <sqlite-users@sqlite.org> > Sent: Tuesday, October 20, 2009 3:06:01 PM GMT -06:00 US/Canada Central > Subject: Re: [sqlite] Crash on freeing mutex in sqlite3.c > > The only place I see this line in SQLite's code is > sqlite3_initialize(). So your path given to sqlite3_open_v2() is > completely irrelevant and FTR no other process "can have a mutex" so > that it will lead to crash of your process. The problem is that your > application corrupts memory. Run it under valgrind and see where the > problem is. > > Pavel > > On Tue, Oct 20, 2009 at 3:25 PM, Kavita Raghunathan > <kavita.raghunat...@skyfiber.com> wrote: >> Although i have successfully opened the database several times, >> today I'm seeing crashes on this line when I use sqlite3_open_v2: >> >> sqlite3_mutex_free(sqlite3GlobalConfig.pInitMutex); >> >> Any ideas what I could be doing wrong to cause this crash ? >> >> Here is the exact way I'm using this C wrapper: >> sqlite3_open_v2(db_filename, &EntityDB, >> SQLITE_OPEN_READWRITE|SQLITE_OPEN_FULLMUTEX, NULL) >> >> >> Things I've already tried: >> 1) Killed any processes that are still running that might have the mutex >> 2) Checked to see if I have a valid file name and path, I'm using /tmp/abc.db >> >> Thanks, >> Kavita >> >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users@sqlite.org >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users >> > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
