Re: gdba probs

[Stefan Monnier]

> I don't know exactly what happens if gdba starts without "--annotate=2" but
> the annotations are needed to tell it the status of the prgram. "--fullname"
> just gives line information for display of the source.

I understand that.  But the `M-x gdb' subset of `M-x gdba' should still
work if you pass `-fullname'.  The rest of course won't, but that's OK:
you get what you asked for.

> Looking at it, gdba doesn't freeze but to seems expect its input to come from
> the input/output buffer (try, for example, typing break main in there)

Interesting.

>  > I understand that with "gdb --fullname foo" most things won't work, but I'd
>  > like to slowly merge M-x gdb and M-x gdba, so I think that the gdba
>  > code should be made to work even if the underlying gdb process is not
>  > configured as expected: it should then behave more or less like M-x gdb 
> does.
> 
> You could infer how gdb was running from the lack/type of annotations (=1, =2)
> but I don't think this would be easy. At the moment I run two gdb commands
> requiring annotations *before* the executable is run to find out in what
> file main is stored.

And probably more in order to get the initial `info breakpoints'
and things like that.
That should just result in error messages or other unexpected output
in the *gdb* buffer, but without breaking the command-line prompt behavior.


        Stefan