[Debian-med-packaging] Bug#845753: Possible workaround

[Dirk Eddelbuettel]

On 15 December 2016 at 14:42, Christian Seiler wrote:
| On 12/15/2016 02:37 PM, Dirk Eddelbuettel wrote:
| > On 15 December 2016 at 14:26, Andreas Tille wrote:
| > | Sorry, but I have no idea how since I'm totally clueless currently and
| > | upstream also did not yet responded to this after the initial idea that
| > | it might be some ape related issue was not helpful.  Do you in turn see
| > | any chance to push this question to the right forum in the R community?
| > 
| > Not really. All (well, most) builds at their are fine [1]. They would likely suggest that
| > we sort our (local to them) issues out at our end.
| > 
| > How to run R with gdb is discussed iin Writing R Extensions.  Maybe we need
| > to start with some stacktraces to see who calls whom how.
| 
| I had already posted a gdb backtrace here:
| https://lists.debian.org/debian-mentors/2016/12/msg00412.html
| 
| Any idea how to get the corresponding R backtrace from this?
| 
| (R's own debug() will obviously not work if there's a C stack
| overflow.)

Use

  R -d gdb [other options you may use]

which is describe in the manual I referenced earlier:
https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Debugging-compiled-code

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org