On 3/2/23 02:56, Tom Tromey wrote:
>>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
> 
> Tom> As for syntax, I went now first for the simplest approach, an on/off
> Tom> setting:
> Tom> ...
> Tom> set always-read-ctf <on|off>
> Tom> ...
> Tom> which itself for instance could be reformulated as read-ctf-always or
> Tom> ctf-read-always, I'm not sure if there's a preferred scheme for things
> Tom> like that.
> 
> Is it something normal users will want?  If not we can make it a maint
> setting and then our future options are open.
> 

I think normal users will want it.

On openSUSE, due the the startfiles containing DWARF, a simple exec 
created with:
...
$ gcc -gctf hello.c
...
will contain both dwarf and ctf, and gdb will only read the dwarf.

There are a couple of ways to get around that:
- use -nostartfiles/-nostdlib, or
- use Wl,--strip-debug
- use strip -g

But eventually, somebody will be in the position of having to debug an 
exec containing both dwarf and ctf, and needing info from both.

> Tom> Furthermore, I wonder, if we want to keep the possibility open of
> Tom> adding additional ways to handle this in the future, should we go
> Tom> instead with something like:
> Tom> ...
> Tom> set read-ctf <no-dwarf2|yes>
> 
> We can always turn it into a deprecated alias and rename it if we later
> change our minds, so I wouldn't worry excessively about it.

Ack, in that case let's go with the current approach.

I've updated the doc by mentioning the default, and added a NEWS item.

Eli, could you please review the doc and NEWS bits?

Thanks,
- Tom