Re: [Rcpp-devel] R.e. Debugging Rcpp packages with GDB

2011-01-25 Thread Douglas Bates
On Mon, Jan 24, 2011 at 9:10 PM, Andrew Redd wrote: > Davor, > A good place to start might be to mirror the behavior of the str in base R. >  That gives quick truncated information, the kind that is helpful in > debugging. > -Andrew There is an internal function in R called inspect that does some

Re: [Rcpp-devel] R.e. Debugging Rcpp packages with GDB

2011-01-24 Thread Andrew Redd
Davor, A good place to start might be to mirror the behavior of the str in base R. That gives quick truncated information, the kind that is helpful in debugging. -Andrew On Mon, Jan 24, 2011 at 7:55 PM, Dirk Eddelbuettel wrote: > > On 24 January 2011 at 16:36, Davor Cubranic wrote: > | To fol

Re: [Rcpp-devel] R.e. Debugging Rcpp packages with GDB

2011-01-24 Thread Dirk Eddelbuettel
On 24 January 2011 at 16:36, Davor Cubranic wrote: | To follow up my original post, it is possible to define GDB pretty-printers using Python. (See http://sourceware.org/gdb/onlinedocs/gdb/Pretty-Printing.html.) Would people be interested in having Rcpp-specific pretty printers? That would be

Re: [Rcpp-devel] R.e. Debugging Rcpp packages with GDB

2011-01-24 Thread Davor Cubranic
To follow up my original post, it is possible to define GDB pretty-printers using Python. (See http://sourceware.org/gdb/onlinedocs/gdb/Pretty-Printing.html.) Would people be interested in having Rcpp-specific pretty printers? Davor On 2011-01-19, at 7:01 AM, Dirk Eddelbuettel wrote: > > On

Re: [Rcpp-devel] R.e. Debugging Rcpp packages with GDB

2011-01-19 Thread Christian Gunning
Thanks all for the crash course - it works great! I just cobbled up a simple "reload" function. This has been a long-standing pet peeve of mine -- anything that makes me leave the R shell is distracting. I've tested it and it seems to work just fine. Are there any non-obvious downsides here? rel

Re: [Rcpp-devel] R.e. Debugging Rcpp packages with GDB

2011-01-19 Thread Dirk Eddelbuettel
On 19 January 2011 at 08:43, Douglas Bates wrote: | > | 2) Is there a simple way to include debugging symbols/keep values from | > | getting optimized out when building with Rcpp? | > | > You could always include -g and then strip what you don't need -- which is | > what Debian and Ubuntu do to gi

Re: [Rcpp-devel] R.e. Debugging Rcpp packages with GDB

2011-01-19 Thread Douglas Bates
On Tue, Jan 18, 2011 at 6:19 PM, Dirk Eddelbuettel wrote: > > On 18 January 2011 at 15:52, Christian Gunning wrote: > | On Tue, Jan 18, 2011 at 2:46 PM, > | wrote: > | > > | > Can people share any tricks they use to debug Rcpp packages? For example, > can I "print" variables in a format that's a

Re: [Rcpp-devel] R.e. Debugging Rcpp packages with GDB

2011-01-18 Thread Dirk Eddelbuettel
On 18 January 2011 at 15:52, Christian Gunning wrote: | On Tue, Jan 18, 2011 at 2:46 PM, | wrote: | > | > Can people share any tricks they use to debug Rcpp packages? For example, can I "print" variables in a format that's a bit more high-level, like something that I would get if I sent them to

[Rcpp-devel] R.e. Debugging Rcpp packages with GDB

2011-01-18 Thread Christian Gunning
On Tue, Jan 18, 2011 at 2:46 PM, wrote: > > Can people share any tricks they use to debug Rcpp packages? For example, can > I "print" variables in a format that's a bit more high-level, like something > that I would get if I sent them to "cout"? > It's not very sophisticated, but I find that mu