OK, how about a backtrace?
On Mon, Jul 20, 2009 at 8:24 PM, Thiago Farina wrote:
>
> Yes, I'm compiling the code under debug build option.
> Everytime I try to type in omnibox this happens.
>
> On Jul 20, 4:02 pm, Scott Hess wrote:
>> Looks to me like the code in question wouldn't be compiled in
Yes, I'm compiling the code under debug build option.
Everytime I try to type in omnibox this happens.
On Jul 20, 4:02 pm, Scott Hess wrote:
> Looks to me like the code in question wouldn't be compiled into
> release builds in the first place (it's under NDEBUG). So it might be
> problematic to
Looks to me like the code in question wouldn't be compiled into
release builds in the first place (it's under NDEBUG). So it might be
problematic to match it to a known bug, since the known bugs would
mostly look different.
The general case of "Started typing in omnibox and crashed" is
obviously
I thought this problem was known.
Thanks!
On Jul 19, 6:33 pm, Peter Kasting wrote:
> On Sun, Jul 19, 2009 at 12:52 PM, Thiago Farina
> wrote:
>
> > When I start typing in omnibox from Chromium (I'm debugging) the
> > browser crashes...
>
> Since yo're debugging, you can track down what's going
On Sun, Jul 19, 2009 at 2:43 PM, Thiago Farina wrote:
> How can I track down?
Using your handy debugger, to see what's going on.
If you don't know how to debug code, you're probably not going to be
well-served by trying to get low-level details from this mailing list.
Where is bug database loc
Hi Peter,
How can I track down?
Where is bug database located? In the Local\Chromium\User Data\Crash
Reports directory, there is nothing.
Thanks!
On Jul 19, 6:33 pm, Peter Kasting wrote:
> On Sun, Jul 19, 2009 at 12:52 PM, Thiago Farina
> wrote:
>
> > When I start typing in omnibox from Chro
On Sun, Jul 19, 2009 at 12:52 PM, Thiago Farina wrote:
> When I start typing in omnibox from Chromium (I'm debugging) the
> browser crashes...
Since yo're debugging, you can track down what's going on.
Then you can look it up in the bug database.
PK
--~--~-~--~~~--
