This is the mail archive of the gdb-patches@sourceware.org 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] |
On 2018-08-09 14:29, Simon Marchi wrote:
On 2018-08-08 09:34, Simon Marchi wrote:Just to put yet another option on the table: since "size" parameter is only used to allocate some space for the collect function to dump the register data in, what about making the collect functions allocate that space themselves. For example, by making them return a gdb::byte_vector.Just to let you know, I've started to play with this idea, see this branch (still very crude): https://github.com/simark/binutils-gdb/commits/regset Please let me know what you think. Does it actually help in your case, and is it a good way to go in general? Simon
Oh, something that looks like a blocker already is that collect functions need to be able to write a single register in an existing buffer (leaving the other ones untouched). If they return an allocated gdb::byte_vector, that doesn't seem possible.
Simon
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |