patches/gdb/6.3/720-debian_static-threads-test.patch
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun May 20 13:48:26 2007 +0000 (2007-05-20)
changeset 112 ea15433daba0
permissions -rw-r--r--
Ah! I finally have a progress bar that doesn't stall the build!
- pipe size in Linux is only 8*512=4096 bytes
- pipe size is not setable
- when the feeding process spits out data faster than the eating
process can read it, then the feeding process stalls after 4KiB
of data sent to the pipe
- for us, the progress bar would spawn a sub-shell every line,
and the sub-shell would in turn spawn a 'date' command.
Which was sloooww as hell, and would cause some kind of a
starvation: the pipe was full most of the time, and the
feeding process was stalled all this time.

Now, we use internal variables and a little hack based onan offset
to determine the elapsed time. Much faster this way, but still
CPU-intensive.
     1 Update staticthreads.exp to handle debugging info in libpthread.a.
     2 
     3 Index: gdb-6.3/gdb/testsuite/gdb.threads/staticthreads.exp
     4 ===================================================================
     5 --- gdb-6.3.orig/gdb/testsuite/gdb.threads/staticthreads.exp	2004-11-10 10:35:15.000000000 -0500
     6 +++ gdb-6.3/gdb/testsuite/gdb.threads/staticthreads.exp	2004-11-10 11:22:48.671121466 -0500
     7 @@ -53,6 +53,10 @@ gdb_test_multiple "continue" "$test" {
     8      -re " sem_post .*$gdb_prompt " {
     9  	pass "$test"
    10      }
    11 +    -re " (.*_)sem_post .*$gdb_prompt " {
    12 +	# Glibc uses aliases for internal symbols; match __new_sem_post.
    13 +	pass "$test"
    14 +    }
    15      -re "Program received signal .*$gdb_prompt " {
    16  	kfail gdb/1328 "$test"
    17      }
    18 @@ -64,8 +68,16 @@ gdb_test_multiple "continue" "$test" {
    19  
    20  rerun_to_main
    21  gdb_test "handle SIG32 nostop noprint pass"
    22 -set test "Handle SIG32 helps"
    23 -gdb_test "continue" " sem_post .*" "handle SIG32 helps"
    24 +set test "handle SIG32 helps"
    25 +gdb_test_multiple "continue" "$test" {
    26 +    -re " sem_post .*$gdb_prompt $" {
    27 +	pass "$test"
    28 +    }
    29 +    -re " (.*_)sem_post .*$gdb_prompt $" {
    30 +	# Glibc uses aliases for internal symbols; match __new_sem_post.
    31 +	pass "$test"
    32 +    }
    33 +}
    34  
    35  
    36  # See if info threads produces anything approaching a thread list.