|
|
|
Created:
15 years, 10 months ago by Collin Winter Modified:
15 years, 10 months ago Reviewers:
Jeffrey Yasskin CC:
unladen-swallow_googlegroups.com Base URL:
http://unladen-swallow.googlecode.com/svn/trunk/ Visibility:
Public. |
Without this, gdb hangs forever, waiting for you to tell it to make the breakpoint pending on a future library load.
Normal (ie, without --enable-shared) builds still pass the test.
Patch Set 1 #
Total comments: 2
Patch Set 2 : Address jyasskin's comments #Total messages: 3
|
Collin Winter
PTAL
|
15 years, 10 months ago (2010年03月10日 00:19:36 UTC) #1 |
PTAL
http://codereview.appspot.com/377041/diff/1/2 File Lib/test/test_jit_gdb.py (right): http://codereview.appspot.com/377041/diff/1/2#newcode49 Lib/test/test_jit_gdb.py:49: "--eval-command=run", You should be able to use "start" instead of "run" to run to main, at which point the shared libraries should be loaded. If that doesn't work, this is fine.
Committing, thanks for the quick review. http://codereview.appspot.com/377041/diff/1/2 File Lib/test/test_jit_gdb.py (right): http://codereview.appspot.com/377041/diff/1/2#newcode49 Lib/test/test_jit_gdb.py:49: "--eval-command=run", On 2010年03月10日 00:33:19, Jeffrey Yasskin wrote: > You should be able to use "start" instead of "run" to run to main, at which > point the shared libraries should be loaded. If that doesn't work, this is fine. Done.