monga at debian.org
Wed Jul 7 07:05:40 UTC 2010
I attached to this message a minimalistic failure test case. You
should be able to reproduce the failure with the following recipe
$ LANG=C chromium-browser test.html
# select 'inspect element' from right-click menu
# select 'Scripts'
# select 'test.html'
# put a breakpoint on line 7 (by clicking on it)
# push reload button
# I get the 'Aw, Snap!' page with the generic error message
# Segfault info is available in the system logs
[15594.289025] chromium-browse: segfault at 0 ip
00007f700fe69b00 sp 00007fff69b9fc00 error 4 in
Is this enough to isolate properly the problem? Thank you!
On Sun, Jun 27, 2010 at 2:27 PM, Jonathan Nieder <jrnieder at gmail.com> wrote:
> Hi Mattia,
> Giuseppe Iuculano wrote:
>> On 06/04/2010 05:42 PM, Mattia Monga wrote:
>>> page is loaded crashes if a breakpoint is activated.
>>> My /var/log/messages reports
>>> chromium-browse: segfault at 0 ip 00007fddd5b3f8a0 sp
>>> 00007ffff2d05c50 error 4 in libv8.so.2.2.7[7fddd5a0d000+273000]
>> thanks for your bug report.
>> Could you provide a proper backtrace please?
> Alternatively, a precise reproduction recipe could be helpful.
> program, set a breakpoint, and let it get activated, but step-by-step
> instructions would make it much easier for novices like me to actually
> do that without investing too much time.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pkg-chromium-maint