Could you please extend dr command to accept optional argument to dump only specific register?

dumping a single register basically takes as long as dumping all of
them. therefore i don't see the advantage of doing that.
why do you need it?

bobef wrote:
> Could you please extend dr command to accept optional argument to dump only specific register?

Because I am writing a front end for ddbg and it supports breakpoint conditions. I wish to enable the user to compare the value of a register in  given condition, so I don't need to parse the output for all registers, but if you say it takes the same time there is really not much point...

Jascha Wetzel <[firstname]@mainia.de> Wrote:

> dumping a single register basically takes as long as dumping all of
> them. therefore i don't see the advantage of doing that.
> why do you need it?
> 
> bobef wrote:
> > Could you please extend dr command to accept optional argument to dump only specific register?

well, parsing is somewhat slower when all registers are ouput, of
course. but the way you're realizing conditional breakpoints is
inherently slow anyway.
i'd suggest to postpone that until Ddbg provides proper conditional
breakpoint support.

bobef wrote:
> Because I am writing a front end for ddbg and it supports breakpoint conditions. I wish to enable the user to compare the value of a register in  given condition, so I don't need to parse the output for all registers, but if you say it takes the same time there is really not much point...
> 
> Jascha Wetzel <[firstname]@mainia.de> Wrote:
> 
>> dumping a single register basically takes as long as dumping all of
>> them. therefore i don't see the advantage of doing that.
>> why do you need it?
>>
>> bobef wrote:
>>> Could you please extend dr command to accept optional argument to dump only specific register?
>