[patch] Indirect access to GDB history variables

Steve Rodrigues steverod@netapp.com
Mon Dec 18 05:46:00 GMT 2006


Daniel Jacobowitz wrote on Sat, Dec 16, 2006 at 01:45:08PM -0500:
> > > I think that we should take the long-postponed jump to embedding
> > > scripting languages, rather than adding more complexity to the existing
> > > CLI.
> > 

...[further discussion]...

I assume that with the embedded scripting language, you'd allow input in a 
'interpreted' fashion; i.e. at the gdb prompt I could enter a Perl or 
Python or Guile command directly, accessing (for example, with Perl) @history or 
$history[$i]?

Would the embedded language support current CLI scripts or not?
I.e. if I have Perl-GDB, can I run my existing GDB scripts or only
Perl-ized versions of them?  (We have quite a large pile and
migrating them to something else probably won't happen, at least in
any reasonable timeframe.)

> -- 
> Daniel Jacobowitz
> CodeSourcery

Thanks,

--Steve
-- 
Steven Rodrigues           | Lost, yesterday, somewhere between sunrise and 
Member of Technical Staff  | sunset, two golden hours, each set with sixty
Network Appliance Corp.    | diamond minutes. No reward is offered, for they
steverod@netapp.com        | are gone forever. -- Horace Mann



More information about the Gdb-patches mailing list