00:09:44  * wingoquit (Ping timeout: 252 seconds)
00:10:06  * dexterfooquit (Ping timeout: 264 seconds)
00:12:46  * dexterfoojoined
00:12:53  * wingojoined
00:34:47  <trungl-bot>Tree closed by buildbot@chromium.org: closed (https://ci.chromium.org/p/v8/builders/ci/V8%20Arm%20-%20debug/9271 from 821bc649515c3d6f1c702ceff61a546e99f899d4)
01:27:12  <trungl-bot>Tree opened by bbudge@google.com: open
01:35:21  * APKjoined
01:35:27  * AKPWDquit (Ping timeout: 245 seconds)
02:31:29  * plutoniixjoined
03:56:27  * cloudshuquit (Quit: Connection closed for inactivity)
04:02:22  * RT|Chatzillaquit (Read error: Connection reset by peer)
05:55:34  * xyz6991[m]joined
05:56:52  * xyz6991[m]part ("User left")
06:47:17  * plutoniixquit (Quit: Leaving)
11:13:21  * AtumTjoined
11:19:28  * RT|Chatzillajoined
12:26:47  * dobsonquit (Quit: Leaving)
12:30:13  * dobsonjoined
12:47:59  <jnes>hello there! how come setting a breakpoint in the beginning of an optimized function causes the code to crash? using d8 + gdb
16:03:53  <caitp>jnes: you mean like at the beginning of turbofanned code?
16:04:41  <caitp>with like an Int3 op or something?
16:10:38  * RT|Chatzillaquit (Quit: ChatZilla 0.9.86.1 [Firefox 2.0.0.22pre/2016020300])
16:33:33  <jnes>hmm yea it went to call Abort in the prologue somehow.. now it's not happening anymore... hmmmmm haha
16:33:59  <jnes>maybe gdb does something that i'm not aware of
16:37:14  <caitp>is it getting to Abort via Runtime_Abort?
16:41:26  <caitp>if the function you're breaking at is a Generator, Runtime_Abort gets called if the resume index wants to jump to a non existent resume point, so could be that?
16:45:10  <jnes>don't know really! will find out.. eventually :)
16:47:34  <caitp>just type `bt` in gdb when it crashes I think :p that should figure where it's coming form
16:47:35  <caitp>from
17:06:57  * APKchanged nick to AKPWD
19:08:28  * cloudshujoined
22:21:00  * AtumTquit (Read error: Connection reset by peer)
22:43:04  * RT|Chatzillajoined
23:13:47  * plutoniixjoined