Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
* [RFA/testsuite] Allow __libc_start_main above main in annota1.exp
@ 2002-01-09 16:05 Daniel Jacobowitz
  2002-01-09 16:41 ` Andrew Cagney
  2002-01-29 21:57 ` Daniel Jacobowitz
  0 siblings, 2 replies; 12+ messages in thread
From: Daniel Jacobowitz @ 2002-01-09 16:05 UTC (permalink / raw)
  To: gdb-patches

From the "annoying testsuite failures cleanup" department - if anyone has a
bright idea on how to write annota tests in a more readable, less
long-single-line fashion, I'd love to hear it.  This fixes the test on all
my compiler/debug combinations, i386-linux.  OK to commit?

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

2002-01-09  Daniel Jacobowitz  <drow@mvista.com>

	* gdb.base/annota1.exp (backtrace from shlibrary): Fix spelling. 
	Allow a start function above main.

Index: annota1.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/annota1.exp,v
retrieving revision 1.7
diff -u -p -r1.7 annota1.exp
--- annota1.exp	2001/12/20 16:52:07	1.7
+++ annota1.exp	2002/01/09 23:53:35
@@ -247,8 +247,8 @@ gdb_expect {
 #
 send_gdb "backtrace\n"
 gdb_expect {
-  -re "\r\n\032\032post-prompt\r\n\r\n\032\032frame-begin 0 $hex\r\n.0  \r\n(\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n)*\032\032frame-function-name\r\nprintf\r\n\032\032frame-args\r\n \\(.*frame-end\r\n\r\n\032\032frame-begin 1 $hex\r\n.1  \r\n\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n\032\032frame-function-name\r\nmain\r\n\032\032frame-args\r\n \\(\\)\r\n\032\032frame-source-begin\r\n at \r\n\032\032frame-source-file\r\n${srcdir}/${subdir}/${srcfile}\r\n\032\032frame-source-file-end\r\n:\r\n\032\032frame-source-line\r\n.*\r\n\032\032frame-source-end\r\n\r\n\r\n\032\032frame-end\r\n$gdb_prompt$" \
-	  { pass "bactrace from shlibrary" }
+  -re "\r\n\032\032post-prompt\r\n\r\n\032\032frame-begin 0 $hex\r\n.0  \r\n(\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n)*\032\032frame-function-name\r\nprintf\r\n\032\032frame-args\r\n \\(.*frame-end\r\n\r\n\032\032frame-begin 1 $hex\r\n.1  \r\n\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n\032\032frame-function-name\r\nmain\r\n\032\032frame-args\r\n \\(\\)\r\n\032\032frame-source-begin\r\n at \r\n\032\032frame-source-file\r\n${srcdir}/${subdir}/${srcfile}\r\n\032\032frame-source-file-end\r\n:\r\n\032\032frame-source-line\r\n.*\r\n\032\032frame-source-end\r\n\r\n\r\n\032\032frame-end\r\n(\r\n\032\032frame-begin .*\r\n\r\n\032\032frame-end\r\n)*$gdb_prompt$" \
+	  { pass "backtrace from shlibrary" }
   -re ".*$gdb_prompt$"     { fail "backtrace from shlibrary" }
   timeout	            { fail "backtrace from shlibrary (timeout)" }
 }


^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [RFA/testsuite] Allow __libc_start_main above main in annota1.exp
  2002-01-09 16:05 [RFA/testsuite] Allow __libc_start_main above main in annota1.exp Daniel Jacobowitz
@ 2002-01-09 16:41 ` Andrew Cagney
  2002-01-29 21:57 ` Daniel Jacobowitz
  1 sibling, 0 replies; 12+ messages in thread
From: Andrew Cagney @ 2002-01-09 16:41 UTC (permalink / raw)
  To: Daniel Jacobowitz; +Cc: gdb-patches

>>From the "annoying testsuite failures cleanup" department - if anyone has a
> bright idea on how to write annota tests in a more readable, less
> long-single-line fashion, I'd love to hear it.  This fixes the test on all
> my compiler/debug combinations, i386-linux.  OK to commit?
> 

Have a look at gdb_expect_list().

Andrew




^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [RFA/testsuite] Allow __libc_start_main above main in annota1.exp
  2002-01-09 16:05 [RFA/testsuite] Allow __libc_start_main above main in annota1.exp Daniel Jacobowitz
  2002-01-09 16:41 ` Andrew Cagney
@ 2002-01-29 21:57 ` Daniel Jacobowitz
  2002-01-29 22:59   ` Kevin Buettner
  2002-02-09  8:19   ` Jim Blandy
  1 sibling, 2 replies; 12+ messages in thread
From: Daniel Jacobowitz @ 2002-01-29 21:57 UTC (permalink / raw)
  To: gdb-patches

On Wed, Jan 09, 2002 at 07:06:28PM -0500, Daniel Jacobowitz wrote:
> >From the "annoying testsuite failures cleanup" department - if anyone has a
> bright idea on how to write annota tests in a more readable, less
> long-single-line fashion, I'd love to hear it.  This fixes the test on all
> my compiler/debug combinations, i386-linux.  OK to commit?

Anyone?

> 2002-01-09  Daniel Jacobowitz  <drow@mvista.com>
> 
> 	* gdb.base/annota1.exp (backtrace from shlibrary): Fix spelling. 
> 	Allow a start function above main.
> 
> Index: annota1.exp
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.base/annota1.exp,v
> retrieving revision 1.7
> diff -u -p -r1.7 annota1.exp
> --- annota1.exp	2001/12/20 16:52:07	1.7
> +++ annota1.exp	2002/01/09 23:53:35
> @@ -247,8 +247,8 @@ gdb_expect {
>  #
>  send_gdb "backtrace\n"
>  gdb_expect {
> -  -re "\r\n\032\032post-prompt\r\n\r\n\032\032frame-begin 0 $hex\r\n.0  \r\n(\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n)*\032\032frame-function-name\r\nprintf\r\n\032\032frame-args\r\n \\(.*frame-end\r\n\r\n\032\032frame-begin 1 $hex\r\n.1  \r\n\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n\032\032frame-function-name\r\nmain\r\n\032\032frame-args\r\n \\(\\)\r\n\032\032frame-source-begin\r\n at \r\n\032\032frame-source-file\r\n${srcdir}/${subdir}/${srcfile}\r\n\032\032frame-source-file-end\r\n:\r\n\032\032frame-source-line\r\n.*\r\n\032\032frame-source-end\r\n\r\n\r\n\032\032frame-end\r\n$gdb_prompt$" \
> -	  { pass "bactrace from shlibrary" }
> +  -re "\r\n\032\032post-prompt\r\n\r\n\032\032frame-begin 0 $hex\r\n.0  \r\n(\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n)*\032\032frame-function-name\r\nprintf\r\n\032\032frame-args\r\n \\(.*frame-end\r\n\r\n\032\032frame-begin 1 $hex\r\n.1  \r\n\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n\032\032frame-function-name\r\nmain\r\n\032\032frame-args\r\n \\(\\)\r\n\032\032frame-source-begin\r\n at \r\n\032\032frame-source-file\r\n${srcdir}/${subdir}/${srcfile}\r\n\032\032frame-source-file-end\r\n:\r\n\032\032frame-source-line\r\n.*\r\n\032\032frame-source-end\r\n\r\n\r\n\032\032frame-end\r\n(\r\n\032\032frame-begin .*\r\n\r\n\032\032frame-end\r\n)*$gdb_prompt$" \
> +	  { pass "backtrace from shlibrary" }
>    -re ".*$gdb_prompt$"     { fail "backtrace from shlibrary" }
>    timeout	            { fail "backtrace from shlibrary (timeout)" }
>  }
> 

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [RFA/testsuite] Allow __libc_start_main above main in annota1.exp
  2002-01-29 21:57 ` Daniel Jacobowitz
@ 2002-01-29 22:59   ` Kevin Buettner
  2002-01-30  7:01     ` Fernando Nasser
  2002-02-09  8:19   ` Jim Blandy
  1 sibling, 1 reply; 12+ messages in thread
From: Kevin Buettner @ 2002-01-29 22:59 UTC (permalink / raw)
  To: Daniel Jacobowitz, gdb-patches

On Jan 30, 12:57am, Daniel Jacobowitz wrote:

> On Wed, Jan 09, 2002 at 07:06:28PM -0500, Daniel Jacobowitz wrote:
> > >From the "annoying testsuite failures cleanup" department - if anyone has a
> > bright idea on how to write annota tests in a more readable, less
> > long-single-line fashion, I'd love to hear it.  This fixes the test on all
> > my compiler/debug combinations, i386-linux.  OK to commit?
> 
> Anyone?

I think it's fine.  But Fernando's the maintainer, so it's his call...

Kevin


^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [RFA/testsuite] Allow __libc_start_main above main in annota1.exp
  2002-01-29 22:59   ` Kevin Buettner
@ 2002-01-30  7:01     ` Fernando Nasser
  2002-01-30 21:08       ` Daniel Jacobowitz
  0 siblings, 1 reply; 12+ messages in thread
From: Fernando Nasser @ 2002-01-30  7:01 UTC (permalink / raw)
  To: Kevin Buettner; +Cc: Daniel Jacobowitz, gdb-patches

Kevin Buettner wrote:
> 
> On Jan 30, 12:57am, Daniel Jacobowitz wrote:
> 
> > On Wed, Jan 09, 2002 at 07:06:28PM -0500, Daniel Jacobowitz wrote:
> > > >From the "annoying testsuite failures cleanup" department - if anyone has a
> > > bright idea on how to write annota tests in a more readable, less
> > > long-single-line fashion, I'd love to hear it.  This fixes the test on all
> > > my compiler/debug combinations, i386-linux.  OK to commit?
> >
> > Anyone?
> 
> I think it's fine.  But Fernando's the maintainer, so it's his call...
> 
> Kevin

Nobody has any objections, so please check it in.

And thanks for the fix.

Regards,
Fernando


-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [RFA/testsuite] Allow __libc_start_main above main in annota1.exp
  2002-01-30  7:01     ` Fernando Nasser
@ 2002-01-30 21:08       ` Daniel Jacobowitz
  0 siblings, 0 replies; 12+ messages in thread
From: Daniel Jacobowitz @ 2002-01-30 21:08 UTC (permalink / raw)
  To: gdb-patches

On Wed, Jan 30, 2002 at 10:00:48AM -0500, Fernando Nasser wrote:
> Kevin Buettner wrote:
> > 
> > On Jan 30, 12:57am, Daniel Jacobowitz wrote:
> > 
> > > On Wed, Jan 09, 2002 at 07:06:28PM -0500, Daniel Jacobowitz wrote:
> > > > >From the "annoying testsuite failures cleanup" department - if anyone has a
> > > > bright idea on how to write annota tests in a more readable, less
> > > > long-single-line fashion, I'd love to hear it.  This fixes the test on all
> > > > my compiler/debug combinations, i386-linux.  OK to commit?
> > >
> > > Anyone?
> > 
> > I think it's fine.  But Fernando's the maintainer, so it's his call...
> > 
> > Kevin
> 
> Nobody has any objections, so please check it in.
> 
> And thanks for the fix.

Committed, thanks.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [RFA/testsuite] Allow __libc_start_main above main in annota1.exp
  2002-01-29 21:57 ` Daniel Jacobowitz
  2002-01-29 22:59   ` Kevin Buettner
@ 2002-02-09  8:19   ` Jim Blandy
  2002-02-09 14:14     ` Daniel Jacobowitz
  1 sibling, 1 reply; 12+ messages in thread
From: Jim Blandy @ 2002-02-09  8:19 UTC (permalink / raw)
  To: Daniel Jacobowitz; +Cc: gdb-patches


If you apply my FRAME_CHAIN_VALID patch, doesn't that simply eliminate
these failures altogether, since __libc_start_main doesn't appear in
the backtrace?

Daniel Jacobowitz <drow@mvista.com> writes:

> On Wed, Jan 09, 2002 at 07:06:28PM -0500, Daniel Jacobowitz wrote:
> > >From the "annoying testsuite failures cleanup" department - if anyone has a
> > bright idea on how to write annota tests in a more readable, less
> > long-single-line fashion, I'd love to hear it.  This fixes the test on all
> > my compiler/debug combinations, i386-linux.  OK to commit?
> 
> Anyone?
> 
> > 2002-01-09  Daniel Jacobowitz  <drow@mvista.com>
> > 
> > 	* gdb.base/annota1.exp (backtrace from shlibrary): Fix spelling. 
> > 	Allow a start function above main.
> > 
> > Index: annota1.exp
> > ===================================================================
> > RCS file: /cvs/src/src/gdb/testsuite/gdb.base/annota1.exp,v
> > retrieving revision 1.7
> > diff -u -p -r1.7 annota1.exp
> > --- annota1.exp	2001/12/20 16:52:07	1.7
> > +++ annota1.exp	2002/01/09 23:53:35
> > @@ -247,8 +247,8 @@ gdb_expect {
> >  #
> >  send_gdb "backtrace\n"
> >  gdb_expect {
> > -  -re "\r\n\032\032post-prompt\r\n\r\n\032\032frame-begin 0 $hex\r\n.0  \r\n(\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n)*\032\032frame-function-name\r\nprintf\r\n\032\032frame-args\r\n \\(.*frame-end\r\n\r\n\032\032frame-begin 1 $hex\r\n.1  \r\n\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n\032\032frame-function-name\r\nmain\r\n\032\032frame-args\r\n \\(\\)\r\n\032\032frame-source-begin\r\n at \r\n\032\032frame-source-file\r\n${srcdir}/${subdir}/${srcfile}\r\n\032\032frame-source-file-end\r\n:\r\n\032\032frame-source-line\r\n.*\r\n\032\032frame-source-end\r\n\r\n\r\n\032\032frame-end\r\n$gdb_prompt$" \
> > -	  { pass "bactrace from shlibrary" }
> > +  -re "\r\n\032\032post-prompt\r\n\r\n\032\032frame-begin 0 $hex\r\n.0  \r\n(\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n)*\032\032frame-function-name\r\nprintf\r\n\032\032frame-args\r\n \\(.*frame-end\r\n\r\n\032\032frame-begin 1 $hex\r\n.1  \r\n\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n\032\032frame-function-name\r\nmain\r\n\032\032frame-args\r\n \\(\\)\r\n\032\032frame-source-begin\r\n at \r\n\032\032frame-source-file\r\n${srcdir}/${subdir}/${srcfile}\r\n\032\032frame-source-file-end\r\n:\r\n\032\032frame-source-line\r\n.*\r\n\032\032frame-source-end\r\n\r\n\r\n\032\032frame-end\r\n(\r\n\032\032frame-begin .*\r\n\r\n\032\032frame-end\r\n)*$gdb_prompt$" \
> > +	  { pass "backtrace from shlibrary" }
> >    -re ".*$gdb_prompt$"     { fail "backtrace from shlibrary" }
> >    timeout	            { fail "backtrace from shlibrary (timeout)" }
> >  }
> > 
> 
> -- 
> Daniel Jacobowitz                           Carnegie Mellon University
> MontaVista Software                         Debian GNU/Linux Developer


^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [RFA/testsuite] Allow __libc_start_main above main in annota1.exp
  2002-02-09  8:19   ` Jim Blandy
@ 2002-02-09 14:14     ` Daniel Jacobowitz
  0 siblings, 0 replies; 12+ messages in thread
From: Daniel Jacobowitz @ 2002-02-09 14:14 UTC (permalink / raw)
  To: Jim Blandy; +Cc: gdb-patches

I assume so.  But that patch went in, and I'd rather leave it in at
least until we have a policy about what not to display that goes across
all targets.

On Sat, Feb 09, 2002 at 11:21:24AM -0500, Jim Blandy wrote:
> 
> If you apply my FRAME_CHAIN_VALID patch, doesn't that simply eliminate
> these failures altogether, since __libc_start_main doesn't appear in
> the backtrace?
> 
> Daniel Jacobowitz <drow@mvista.com> writes:
> 
> > On Wed, Jan 09, 2002 at 07:06:28PM -0500, Daniel Jacobowitz wrote:
> > > >From the "annoying testsuite failures cleanup" department - if anyone has a
> > > bright idea on how to write annota tests in a more readable, less
> > > long-single-line fashion, I'd love to hear it.  This fixes the test on all
> > > my compiler/debug combinations, i386-linux.  OK to commit?
> > 
> > Anyone?
> > 
> > > 2002-01-09  Daniel Jacobowitz  <drow@mvista.com>
> > > 
> > > 	* gdb.base/annota1.exp (backtrace from shlibrary): Fix spelling. 
> > > 	Allow a start function above main.
> > > 
> > > Index: annota1.exp
> > > ===================================================================
> > > RCS file: /cvs/src/src/gdb/testsuite/gdb.base/annota1.exp,v
> > > retrieving revision 1.7
> > > diff -u -p -r1.7 annota1.exp
> > > --- annota1.exp	2001/12/20 16:52:07	1.7
> > > +++ annota1.exp	2002/01/09 23:53:35
> > > @@ -247,8 +247,8 @@ gdb_expect {
> > >  #
> > >  send_gdb "backtrace\n"
> > >  gdb_expect {
> > > -  -re "\r\n\032\032post-prompt\r\n\r\n\032\032frame-begin 0 $hex\r\n.0  \r\n(\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n)*\032\032frame-function-name\r\nprintf\r\n\032\032frame-args\r\n \\(.*frame-end\r\n\r\n\032\032frame-begin 1 $hex\r\n.1  \r\n\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n\032\032frame-function-name\r\nmain\r\n\032\032frame-args\r\n \\(\\)\r\n\032\032frame-source-begin\r\n at \r\n\032\032frame-source-file\r\n${srcdir}/${subdir}/${srcfile}\r\n\032\032frame-source-file-end\r\n:\r\n\032\032frame-source-line\r\n.*\r\n\032\032frame-source-end\r\n\r\n\r\n\032\032frame-end\r\n$gdb_prompt$" \
> > > -	  { pass "bactrace from shlibrary" }
> > > +  -re "\r\n\032\032post-prompt\r\n\r\n\032\032frame-begin 0 $hex\r\n.0  \r\n(\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n)*\032\032frame-function-name\r\nprintf\r\n\032\032frame-args\r\n \\(.*frame-end\r\n\r\n\032\032frame-begin 1 $hex\r\n.1  \r\n\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n\032\032frame-function-name\r\nmain\r\n\032\032frame-args\r\n \\(\\)\r\n\032\032frame-source-begin\r\n at \r\n\032\032frame-source-file\r\n${srcdir}/${subdir}/${srcfile}\r\n\032\032frame-source-file-end\r\n:\r\n\032\032frame-source-line\r\n.*\r\n\032\032frame-source-end\r\n\r\n\r\n\032\032frame-end\r\n(\r\n\032\032frame-begin .*\r\n\r\n\032\032frame-end\r\n)*$gdb_prompt$" \
> > > +	  { pass "backtrace from shlibrary" }
> > >    -re ".*$gdb_prompt$"     { fail "backtrace from shlibrary" }
> > >    timeout	            { fail "backtrace from shlibrary (timeout)" }
> > >  }
> > > 
> > 
> > -- 
> > Daniel Jacobowitz                           Carnegie Mellon University
> > MontaVista Software                         Debian GNU/Linux Developer
> 

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [RFA/testsuite] Allow __libc_start_main above main in annota1.exp
  2002-01-30  8:37 ` Fernando Nasser
  2002-02-09  8:18   ` Jim Blandy
@ 2002-02-09  8:19   ` Jim Blandy
  1 sibling, 0 replies; 12+ messages in thread
From: Jim Blandy @ 2002-02-09  8:19 UTC (permalink / raw)
  To: Fernando Nasser; +Cc: Michael Elizabeth Chastain, drow, gdb-patches


You know, it wouldn't be hard to write another mi-like interface that
used different builders to emit Emacs Lisp s-expressions.  We could
end up with a real killer Emacs interface that way.
 


^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [RFA/testsuite] Allow __libc_start_main above main in annota1.exp
  2002-01-30  8:37 ` Fernando Nasser
@ 2002-02-09  8:18   ` Jim Blandy
  2002-02-09  8:19   ` Jim Blandy
  1 sibling, 0 replies; 12+ messages in thread
From: Jim Blandy @ 2002-02-09  8:18 UTC (permalink / raw)
  To: Fernando Nasser; +Cc: Michael Elizabeth Chastain, drow, gdb-patches


Fernando Nasser <fnasser@redhat.com> writes:
> Michael Elizabeth Chastain wrote:
> > 
> > BTW, the annotation interface is deprecated (see the NEWS file
> > in gdb 5.1.1).  I'm in favor of maintaining test scripts for
> > deprecated features for a while, but I don't feel an urge to
> > solve the "giant annotation line" problem.
> > 
> > Andrew or anyone, can you say how long the annotation interface
> > is going to stay around?
> > 
> 
> I believe as long as emacs uses it.

M-x gdb doesn't use it.  There's no way to know whether anyone's using
the other interface; it could just lie around for years.

I think we should #ifdef out support for the annotation interface, and
see if anyone complains.


^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [RFA/testsuite] Allow __libc_start_main above main in annota1.exp
  2002-01-30  8:02 Michael Elizabeth Chastain
@ 2002-01-30  8:37 ` Fernando Nasser
  2002-02-09  8:18   ` Jim Blandy
  2002-02-09  8:19   ` Jim Blandy
  0 siblings, 2 replies; 12+ messages in thread
From: Fernando Nasser @ 2002-01-30  8:37 UTC (permalink / raw)
  To: Michael Elizabeth Chastain; +Cc: drow, gdb-patches

Michael Elizabeth Chastain wrote:
> 
> BTW, the annotation interface is deprecated (see the NEWS file
> in gdb 5.1.1).  I'm in favor of maintaining test scripts for
> deprecated features for a while, but I don't feel an urge to
> solve the "giant annotation line" problem.
> 
> Andrew or anyone, can you say how long the annotation interface
> is going to stay around?
> 

I believe as long as emacs uses it.

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [RFA/testsuite] Allow __libc_start_main above main in annota1.exp
@ 2002-01-30  8:02 Michael Elizabeth Chastain
  2002-01-30  8:37 ` Fernando Nasser
  0 siblings, 1 reply; 12+ messages in thread
From: Michael Elizabeth Chastain @ 2002-01-30  8:02 UTC (permalink / raw)
  To: drow, gdb-patches

BTW, the annotation interface is deprecated (see the NEWS file
in gdb 5.1.1).  I'm in favor of maintaining test scripts for
deprecated features for a while, but I don't feel an urge to
solve the "giant annotation line" problem.

Andrew or anyone, can you say how long the annotation interface
is going to stay around?

Michael C


^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2002-02-09 22:14 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-01-09 16:05 [RFA/testsuite] Allow __libc_start_main above main in annota1.exp Daniel Jacobowitz
2002-01-09 16:41 ` Andrew Cagney
2002-01-29 21:57 ` Daniel Jacobowitz
2002-01-29 22:59   ` Kevin Buettner
2002-01-30  7:01     ` Fernando Nasser
2002-01-30 21:08       ` Daniel Jacobowitz
2002-02-09  8:19   ` Jim Blandy
2002-02-09 14:14     ` Daniel Jacobowitz
2002-01-30  8:02 Michael Elizabeth Chastain
2002-01-30  8:37 ` Fernando Nasser
2002-02-09  8:18   ` Jim Blandy
2002-02-09  8:19   ` Jim Blandy

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox