[PATCH] Some tracepoint fixes

[Nathan Sidwell]

In porting gdb to a new architecture, I came across a number of core gdb
bugs.   Here is the first set of them and addresses the following issues,

1) we did not allow 'extended-remote' targets to use tracepoints.

2) We could only trace architectures with 64 registers, not 256 like
a comment suggested.

3) There was an erroneous comment about tracing memory ranges

4) If a ^D was entered when entering the 'actions' list, we'd create
a NULL action, which would cause a segfault when tracing started.

5) The 'tstatus' command did not actually print any status. testcase
gdb.trace/tfind.exp exepected it to do so.

6) Parsing the tfind responses uses strtol to read hex.  That reads
'FFFFFFFF' as '7FFFFFFF' (and sets errno).  Using sscanf reads that as
-1, as desired.

built and tested on i686-pc-linux-gnu, (and on the unreleased architecture
I ported to) ok?

nathan


-- 
Nathan Sidwell    ::   http://www.codesourcery.com   ::     CodeSourcery LLC
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: tracepoint1.patch
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20050209/0c706045/attachment.ksh>