Hi,
Vincent Bernat wrote:
> #if defined(OS_POSIX) && !defined(OS_MACOSX)
> RenderProcessImpl render_process;
> render_process.set_main_thread(new RenderThread());
> #endif
>
> Here, I am greeted with:
> waiting for new child: No child processes.
Yes, I get the same thing. Not sure what the cause is.
> Dunno what to do.
Adding "#include <iostream>" to the top of relevant files and putting
std::cerr << "here is some state: " << state << "\n";
at points of interest works. And it's kind of pleasant --- it forces
one to stare at code between runs.
No conclusions yet. Looks like the failure happens in
src/crypto/nss_util.cc, function EnsureNSSInit():
void EnsureNSSInit() {
// Initializing SSL causes us to do blocking IO.
// Temporarily allow it until we fix
// http://code.google.com/p/chromium/issues/detail?id=59847
base::ThreadRestrictions::ScopedAllowIO allow_io;
std::cerr << "This is printed.\n";
g_nss_singleton.Get();
std::cerr << "This is not printed.\n";
}
g_nss_singleton is declared as follows:
base::LazyInstance<NSSInitSingleton,
base::LeakyLazyInstanceTraits<NSSInitSingleton> >
g_nss_singleton(base::LINKER_INITIALIZED);
The next step is to dig into the NSSInitSingleton constructor,
presumably.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
