Sergei Golubchik

Just FYI, this is how I did it — https://github.com/vuvova/gdb-tools/blob/64a9280/duel/parser.py The main grammar starts from [line 52](https://github.com/vuvova/gdb-tools/blob/64a9280/duel/parser.py#L52), note the token `cast` in the [line 72](https://github.com/vuvova/gdb-tools/blob/64a9280/duel/parser.py#L72). And see above how it's...

May be I used an older version? There was `isinstance(..., Match)`, as far as I remember. You can try to inherit with a dummy class, like ``` class MatchChild(Match) pass...

I'm not quite sure how to fit it into the language. In duel one can easily print many values of different types, like ``` (gdb) dl 1,2.0,"foo" ``` or, more...

Thanks. It's not a question of time, it, probably, wouldn't need much time to implement. It's just that I don't understand how to fit the concept of these /x formats...

There is no need to modify the parser as such. I'd do something like ```py if arg.startswith("/x"): hex_mode=True arg=arg[2:] ```

I know. This is one of gdb python API limitations. It can store the "value" (e.g. `head->next->getKey` a pointer to a member method) in a python variable, but it doesn't...

I've just submitted a pull request that allows arbitrary incremental elements: https://github.com/paulrouget/dzslides/pull/116

it's included in (squashed with) e317023

Yes, never mind that. I know it's for bb-11.5-MDEV-32188-timestamps and will take care that it's merged correctly. Either in that branch or in the main after bb-11.5-MDEV-32188-timestamps is pushed

partially included info e317023, the rest is obsolete