]> git.pld-linux.org Git - packages/gdb.git/blob - gdb-6.6-scheduler_locking-step-is-default.patch
- updated (performance fixes).
[packages/gdb.git] / gdb-6.6-scheduler_locking-step-is-default.patch
1 Index: gdb-7.3.50.20110722/gdb/infrun.c
2 ===================================================================
3 --- gdb-7.3.50.20110722.orig/gdb/infrun.c       2011-07-22 19:12:56.000000000 +0200
4 +++ gdb-7.3.50.20110722/gdb/infrun.c    2011-07-22 19:17:06.000000000 +0200
5 @@ -1549,7 +1549,7 @@ static const char *scheduler_enums[] = {
6    schedlock_step,
7    NULL
8  };
9 -static const char *scheduler_mode = schedlock_off;
10 +static const char *scheduler_mode = schedlock_step;
11  static void
12  show_scheduler_mode (struct ui_file *file, int from_tty,
13                      struct cmd_list_element *c, const char *value)
14 Index: gdb-7.3.50.20110722/gdb/testsuite/gdb.mi/mi-console.exp
15 ===================================================================
16 --- gdb-7.3.50.20110722.orig/gdb/testsuite/gdb.mi/mi-console.exp        2011-01-01 16:33:47.000000000 +0100
17 +++ gdb-7.3.50.20110722/gdb/testsuite/gdb.mi/mi-console.exp     2011-07-22 19:17:06.000000000 +0200
18 @@ -47,6 +47,9 @@ if  { [gdb_compile "${srcdir}/${subdir}/
19  
20  mi_run_to_main
21  
22 +# thread-id=\"all\" vs. thread-id=\"1\" below:
23 +mi_gdb_test "210-gdb-set scheduler-locking off" "210\\^done" "set scheduler-locking off"
24 +
25  # Next over the hello() call which will produce lots of output
26  mi_gdb_test "220-exec-next" \
27             "220\\^running(\r\n\\*running,thread-id=\"all\")?" \
28 Index: gdb-7.3.50.20110722/gdb/testsuite/gdb.mi/mi2-console.exp
29 ===================================================================
30 --- gdb-7.3.50.20110722.orig/gdb/testsuite/gdb.mi/mi2-console.exp       2011-06-23 11:40:50.000000000 +0200
31 +++ gdb-7.3.50.20110722/gdb/testsuite/gdb.mi/mi2-console.exp    2011-07-22 19:17:27.000000000 +0200
32 @@ -47,6 +47,9 @@ if  { [gdb_compile "${srcdir}/${subdir}/
33  
34  mi_run_to_main
35  
36 +# thread-id=\"all\" vs. thread-id=\"1\" below:
37 +mi_gdb_test "210-gdb-set scheduler-locking off" "210\\^done" "set scheduler-locking off"
38 +
39  # Next over the hello() call which will produce lots of output
40  mi_gdb_test "220-exec-next" "220\\^running(\r\n)?(\\*running,thread-id=\"all\")?" \
41         "Started step over hello"
42 Index: gdb-7.3.50.20110722/gdb/testsuite/gdb.mi/mi-cli.exp
43 ===================================================================
44 --- gdb-7.3.50.20110722.orig/gdb/testsuite/gdb.mi/mi-cli.exp    2011-04-27 12:17:38.000000000 +0200
45 +++ gdb-7.3.50.20110722/gdb/testsuite/gdb.mi/mi-cli.exp 2011-07-22 19:17:06.000000000 +0200
46 @@ -176,7 +176,7 @@ mi_execute_to "exec-continue" "breakpoin
47  # Test that the token is output even for CLI commands
48  # Also test that *stopped includes frame information.
49  mi_gdb_test "34 next" \
50 -    ".*34\\\^running.*\\*running,thread-id=\"all\"" \
51 +    ".*34\\\^running.*\\*running,thread-id=\"1\"" \
52      "34 next: run"
53  
54  if {!$async} {
This page took 0.729542 seconds and 3 git commands to generate.