From: Bob Rossi <bob@brasko.net>
To: Paul Hilfinger <hilfingr@EECS.Berkeley.EDU>,
GDB <gdb@sources.redhat.com>
Subject: Re: How do I get regexp from expect at gdb_expect?
Date: Mon, 31 Jan 2005 21:10:00 -0000 [thread overview]
Message-ID: <20050131211042.GA8411@white> (raw)
In-Reply-To: <20050131162609.GA19459@nevyn.them.org>
> You've left out your pattern, and the context. I recommend using
> "exp_internal 1" to debug this sort of problem; that will show you what
> expect is doing.
OK, here's an example of the problem, here's the output for 2
consecutive commands given to GDB.
First, 200-break-delete is sent. The '200-break-delete' is in the
'expect_out(buffer)' output, which leads me to believe the testsuite is
echoing the input command. This in itself is probably wrong. However, the
'200-break-delete' is not in the matched regular expression
'expect_out(0,string)'.
The next command, '200-break-list' is in both the 'expect_out(buffer)'
and in the 'expect_out(0,string)'. This leads me to believe that there
is something wrong with the regular expression matching. It can match
things that it shouldn't, which could mask problems.
I don't really understand what you are saying about 'GDB is echoing
commands'. I do understand that when you are at the terminal running
GDB, GDB allows the terminal to 'echo' the char's typed. However, if you
fork/exec GDB, and send it a command, it will not 'echo' the data back
to your process. Isn't this the way Expect works?
The output is below.
Thanks,
Bob Rossi
send: sending "200-break-delete\n" to { exp11 }
expect: does "" (spawn_id exp11) match regular expression "\*\*\* DOSEXIT code.*"? no
"Ending remote debugging.*[(]gdb[)] \r\n[ ]*$"? no
"([\r\n]*((\^done)[\r\n]+[(]gdb[)] \r\n[ ]*$))"? no
"(^FOOBAR$)$"? no
"Undefined.* command:.*[(]gdb[)] \r\n[ ]*$"? no
"Ambiguous command.*[(]gdb[)] \r\n[ ]*$"? no
"Program exited with code [0-9]+.*[(]gdb[)] \r\n[ ]*$"? no
"The program is not being run.*[(]gdb[)] \r\n[ ]*$"? no
".*[(]gdb[)] \r\n[ ]*$"? no
"<return>"? no
"\(y or n\) "? no
full_buffer? no
200-break-delete
200^done
(gdb)
expect: does "200-break-delete\r\n200^done\r\n(gdb) \r\n" (spawn_id exp11) match regular expression "\*\*\* DOSEXIT code.*"? no
"Ending remote debugging.*[(]gdb[)] \r\n[ ]*$"? no
"([\r\n]*((\^done)[\r\n]+[(]gdb[)] \r\n[ ]*$))"? yes
expect: set expect_out(0,string) "^done\r\n(gdb) \r\n"
expect: set expect_out(1,string) "^done\r\n(gdb) \r\n"
expect: set expect_out(2,string) "^done\r\n(gdb) \r\n"
expect: set expect_out(3,string) "^done"
expect: set expect_out(spawn_id) "exp11"
expect: set expect_out(buffer) "200-break-delete\r\n200^done\r\n(gdb) \r\n"
PASS: gdb.mi/mi2-basics.exp: break-delete (all) operation
send: sending "201-break-list\n" to { exp11 }
expect: does "" (spawn_id exp11) match regular expression "\*\*\* DOSEXIT code.*"? no
"Ending remote debugging.*[(]gdb[)] \r\n[ ]*$"? no
"([\r\n]*((.*\^done,BreakpointTable=\{.*,body=\[\]\})[\r\n]+[(]gdb[)] \r\n[ ]*$))"? no
"(^FOOBAR$)$"? no
"Undefined.* command:.*[(]gdb[)] \r\n[ ]*$"? no
"Ambiguous command.*[(]gdb[)] \r\n[ ]*$"? no
"Program exited with code [0-9]+.*[(]gdb[)] \r\n[ ]*$"? no
"The program is not being run.*[(]gdb[)] \r\n[ ]*$"? no
".*[(]gdb[)] \r\n[ ]*$"? no
"<return>"? no
"\(y or n\) "? no
full_buffer? no
201-break-list
201^done,BreakpointTable={nr_rows="0",nr_cols="6",hdr=[{width="3",alignment="-1",col_name="number",colhdr="Num"},{width="14",alignment="-1",col_name="type",colhdr="Type"},{width="4",alignment="-1",col_name="disp",colhdr="Disp"},{width="3",alignment="-1",col_name="enabled",colhdr="Enb"},{width="10",alignment="-1",col_name="addr",colhdr="Address"},{width="40",alignment="2",col_name="what",colhdr="What"}],body=[]}
(gdb)
expect: does "201-break-list\r\n201^done,BreakpointTable={nr_rows="0",nr_cols="6",hdr=[{width="3",alignment="-1",col_name="number",colhdr="Num"},{width="14",alignment="-1",col_name="type",colhdr="Type"},{width="4",alignment="-1",col_name="disp",colhdr="Disp"},{width="3",alignment="-1",col_name="enabled",colhdr="Enb"},{width="10",alignment="-1",col_name="addr",colhdr="Address"},{width="40",alignment="2",col_name="what",colhdr="What"}],body=[]}\r\n(gdb) \r\n" (spawn_id exp11) match regular expression "\*\*\* DOSEXIT code.*"? no
"Ending remote debugging.*[(]gdb[)] \r\n[ ]*$"? no
"([\r\n]*((.*\^done,BreakpointTable=\{.*,body=\[\]\})[\r\n]+[(]gdb[)] \r\n[ ]*$))"? yes
expect: set expect_out(0,string) "201-break-list\r\n201^done,BreakpointTable={nr_rows="0",nr_cols="6",hdr=[{width="3",alignment="-1",col_name="number",colhdr="Num"},{width="14",alignment="-1",col_name="type",colhdr="Type"},{width="4",alignment="-1",col_name="disp",colhdr="Disp"},{width="3",alignment="-1",col_name="enabled",colhdr="Enb"},{width="10",alignment="-1",col_name="addr",colhdr="Address"},{width="40",alignment="2",col_name="what",colhdr="What"}],body=[]}\r\n(gdb) \r\n"
expect: set expect_out(1,string) "201-break-list\r\n201^done,BreakpointTable={nr_rows="0",nr_cols="6",hdr=[{width="3",alignment="-1",col_name="number",colhdr="Num"},{width="14",alignment="-1",col_name="type",colhdr="Type"},{width="4",alignment="-1",col_name="disp",colhdr="Disp"},{width="3",alignment="-1",col_name="enabled",colhdr="Enb"},{width="10",alignment="-1",col_name="addr",colhdr="Address"},{width="40",alignment="2",col_name="what",colhdr="What"}],body=[]}\r\n(gdb) \r\n"
expect: set expect_out(2,string) "201-break-list\r\n201^done,BreakpointTable={nr_rows="0",nr_cols="6",hdr=[{width="3",alignment="-1",col_name="number",colhdr="Num"},{width="14",alignment="-1",col_name="type",colhdr="Type"},{width="4",alignment="-1",col_name="disp",colhdr="Disp"},{width="3",alignment="-1",col_name="enabled",colhdr="Enb"},{width="10",alignment="-1",col_name="addr",colhdr="Address"},{width="40",alignment="2",col_name="what",colhdr="What"}],body=[]}\r\n(gdb) \r\n"
expect: set expect_out(3,string) "201-break-list\r\n201^done,BreakpointTable={nr_rows="0",nr_cols="6",hdr=[{width="3",alignment="-1",col_name="number",colhdr="Num"},{width="14",alignment="-1",col_name="type",colhdr="Type"},{width="4",alignment="-1",col_name="disp",colhdr="Disp"},{width="3",alignment="-1",col_name="enabled",colhdr="Enb"},{width="10",alignment="-1",col_name="addr",colhdr="Address"},{width="40",alignment="2",col_name="what",colhdr="What"}],body=[]}"
expect: set expect_out(spawn_id) "exp11"
expect: set expect_out(buffer) "201-break-list\r\n201^done,BreakpointTable={nr_rows="0",nr_cols="6",hdr=[{width="3",alignment="-1",col_name="number",colhdr="Num"},{width="14",alignment="-1",col_name="type",colhdr="Type"},{width="4",alignment="-1",col_name="disp",colhdr="Disp"},{width="3",alignment="-1",col_name="enabled",colhdr="Enb"},{width="10",alignment="-1",col_name="addr",colhdr="Address"},{width="40",alignment="2",col_name="what",colhdr="What"}],body=[]}\r\n(gdb) \r\n"
next prev parent reply other threads:[~2005-01-31 21:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 2:57 Bob Rossi
2005-01-29 3:09 ` Paul Hilfinger
2005-01-29 3:11 ` Bob Rossi
2005-01-29 3:16 ` Bob Rossi
2005-01-31 15:07 ` Bob Rossi
2005-01-31 16:28 ` Daniel Jacobowitz
2005-01-31 16:59 ` Bob Rossi
2005-01-31 21:10 ` Bob Rossi [this message]
2005-01-31 21:21 ` Daniel Jacobowitz
2005-01-31 22:00 ` Bob Rossi
2005-01-31 22:04 ` Daniel Jacobowitz
2005-01-31 22:12 ` Bob Rossi
2005-02-01 3:52 ` Daniel Jacobowitz
2005-02-01 14:20 ` Bob Rossi
2005-02-01 14:23 ` Daniel Jacobowitz
2005-02-01 14:39 ` Bob Rossi
2005-02-01 15:20 ` Daniel Jacobowitz
2005-02-01 15:38 ` Bob Rossi
2005-02-01 15:58 ` Dave Korn
2005-02-01 16:10 ` 'Bob Rossi'
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050131211042.GA8411@white \
--to=bob@brasko.net \
--cc=gdb@sources.redhat.com \
--cc=hilfingr@EECS.Berkeley.EDU \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox