This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Reporting unsupported things.

On Mon, 2006-04-24 at 16:55 -0400, Daniel Jacobowitz wrote:
> We want to say that reverse execution is not supported.

I have been given a similar request.  My users want to see a message
like "a 32-bit ppc GDB can't debug a 64-bit ppc target program".

In general, it would be nice if GDB could detect that it was being asked
to do something it can't do as soon as it was asked.

This kind of intersects with the multi-arch idea.  With that, GDB
conceptually has a binary matrix where each column would represent a
different target and each row a different host and the cell value would
be true if the GDB configured for the given host could debug the given

If the target is remote, it could tell GDB which column of the matrix is

For a native configuration, perhaps the appropriate row of the matrix
could be built by some config script and the appropriate column could be
chosen based on the type of the executable and/or corefile.  And
'attach' muddies up the water a bit.

I guess what I am suggesting is that GDB have a concrete matrix like
this and consult it as soon as it's known what the user is trying to do.
Of course the 'matrix' would probably really be a hash.

What do you think?

-=# Paul #=-

PS:  In theory, a 32-bit GDB running on a 64-bit ppc host could debug a
64-bit target: "ptrace" allegedly supports this.  The current ppc port,
however, does not.

PPS: Do you know of any other "biarch" configurations of GDB?

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]