On Tue, Mar 20, 2012 at 06:44, C. Mundi <[email protected]> wrote: > I apologize for asking without posting code, but I have not yet finished > isolating the code which throws this. > > Here is the error. No line numbers, no stack trace: > > terminate called after throwing an instance of 'std::bad_alloc' > what(): std::bad_alloc > Aborted > > Does anyone recognize this? Node v0.6.13 on Linux kernel 3.0.0-16 x64. > > What I do know is that node is being asked to allocate about 64 KB when this > happens. The system is absolutely not under memory pressure and the process > VM and RSS are only a few MB bigger than the "quiet" values for node. > > Any advice on how I would start hunting this thing? I have only glanced at > the discussions of node memory management, so go ahead and assume I know > nothing -- it will be close to the truth. Maybe there's a way to instrument > the code with something more clever than console.error?
`backtrace` in gdb will tell you where the exception originates from, `frame #` and `list`, `print`, etc. will let you inspect the code and variables at the call site. Compile with -g, otherwise you won't get debug symbols or line numbers. That's `./configure --debug && make` with v0.6, `make BUILDTYPE=Debug` with master. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
