similar to: Problem with GDB: Cannot find new threads

Hi, We have the error below. Any ideas ? Regards, Matt $ R --vanilla -d gdb GNU gdb 6.7.1-debian Copyright (C) 2007 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying"

In the R-2-9-branch (svn revision 49914, 2009-09-24), R's configure script has an "--enable-threads" option. But, does it do anything useful? When I use "--enable-threads=posix", some of the configure output changes slightly, but it seems to have no effect on the actual link commands used when building R. Is that a bug, or am I misunderstanding what it's supposed to

Hi everyone. I'm trying to learn my way around the R internals. I've gone pretty much as far as I can go with the information given in Writing R Extensions and R Internals, but I still have a lot of questions, too many in fact to post them to the r-devel list. But I think I could answer many of these if I could just step through R's execution during some basic operations. What

On Sat, Jun 19, 2010 at 8:53 PM, Yuri <yuri at rawbw.com> wrote: > I have followed http://llvm.org/docs/DebuggingJITedCode.html, used the > latest release gdb-7.1 (from March 18, 2010) and got this stack: > > (gdb) bt > #0  0x35532156 in ?? () > #1  0x355320f8 in ?? () > #2  0x35532098 in ?? () > #3  0x3553202e in ?? () > #4  0x34a5661a in ?? () > #5  0x349d9bd9

Dear All, We are running RHEL4 Update 4 AS IA-64 on a HP rx6600. We are running programs compiled in RHEL4 Update 4 AS in i386 architecture using the emul library(Intel IA-32 Execution Layer ) [admin at corviewsecondary ~]$ service ia32el status Intel IA-32 Execution Layer in use When we attempt to run a program using /usr/bin/gdb we are not able to hit the break point set. [admin at

Hallo Guys, something went wrong and I didn't know from where. - uninstall vmware (removed to virtual adapter) - reinstall package with route and ping and glibc - test with original kernel and own vanilla nothing helps. Laptop by my side has same software stand no problem at all gdb --args ping benzler.me GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-94.el7 Copyright (C) 2013 Free

Hi John, Yes, it was the problem of the namespace. Sorry for bugging for such a silly mistake. Thanks Pranav On Mon, Apr 19, 2010 at 9:33 AM, John Criswell <criswell at uiuc.edu> wrote: > Pranav Garg wrote: > >> Hi, >> >> I am trying to debug my llvm pass called -aa-eval-garg11 using gdb. >> However I am not able to establish a breakpoint in any function of

I'm having trouble debugging x86 code generated by LLVM. GDB does work with the code, but not correctly, for example, the "next" command does not skip over a function call. Here's an example. Source program gdb1.c: int x; void foo(){ x++; } void bar(){ x--; } int main(){ foo(); bar(); return 0; } commands: $ llvm-gcc -g -emit-llvm -c gdb1.c -o gdb1.bc $ llc

https://bugs.freedesktop.org/show_bug.cgi?id=55832 Priority: medium Bug ID: 55832 Assignee: nouveau at lists.freedesktop.org Summary: xf86-video-nouveau-1.0.2 - Xorg crashes once a week : segmentation fault in NVRefreshArea QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified

http://puffy.homelinux.org/~gnumdk/compiz/patch/place.patch Here a new version of my patch. It now have six placement mode (kwin placement modes): - Cascade - Centered - Random - LeftCorner - Maximize - Smart Currently, smart placement isn't present in this patch. I'm working on it but my ubuntu(feisty) have really strange behaviours ... I can't debug compiz anymore.

I'm trying to run the example described at: http://llvm.org/docs/DebuggingJITedCode.html I followed the sample command line session (below, with versions numbers for everything), but gdb doesn't stop at the breakpoints as described. Any idea what is wrong? Thanks, Zach zdevito at derp:~/terra/tests$ > ~/clang+llvm-3.4-x86_64-unknown-ubuntu12.04/bin/clang -cc1 -O0 -g >

Hi! When I issue: doveadm fts expand -A body xxx I'm always getting Segfault. I can't find descrption of this command in manual, is it possible to add some information to manual? # gdb -q doveadm Reading symbols from doveadm...Reading symbols from /usr/lib64/debug//usr/bin/doveadm.debug...done. done. (gdb) set args fts expand -A body XXX (gdb) run Starting program: /usr/bin/doveadm fts

> > I wonder if abi::__cxa_demangle guarantees unambigous names? >> > > No, it does not. > Interesting. Can you give an example of type where it fails? I'm currently working on hardware construction library for C++ (similar to Chisel (which is written in Scala)). And since C++ has no standardized reflection, I use DWARF as a source of reflection metadata. And in case of

Dear developers I get some strange crashes when 'cairoDevice' and 'tcltk' are both loaded in the same R vanilla session. When executing the following in that order require(relimp) require(cairoDevice) showData (iris) I get a crash with the following message (see R-relimp-cairoDevice.txt): The program 'R' received an X Window System error. This probably reflects a bug in

https://bugs.freedesktop.org/show_bug.cgi?id=97537 Bug ID: 97537 Summary: nvc0 occasionally crashes in glDrawArrays in a multi-threaded app Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:

Pranav Garg wrote: > Hi, > > I am trying to debug my llvm pass called -aa-eval-garg11 using gdb. > However I am not able to establish a breakpoint in any function of my > pass. I have compiled my > pass with a debug build and I have also compiled the input file (using > llvm-gcc) with the -g flag. Given below is the exact output. > > > (gdb) break

OK I find out how to extract core dump (sorry), hope this will help you. gdb /usr/lib/dovecot/auth /var/core/core.28304 GNU gdb (Debian 7.12-6) 7.12.0.20161007-git Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the

Right now, GDB has no way to be told about JITed code. I'm working on adding such an interface, and the LLVM JIT would be the first client. The interface is evolving, and I'll admit that right now it's downright terrible. Here's how it works right now: - The JIT generates the machine code and DWARF call frame info (.eh_frame/.debug_frame) for a function into memory. - The JIT

Hi, I am trying to debug my llvm pass called -aa-eval-garg11 using gdb. However I am not able to establish a breakpoint in any function of my pass. I have compiled my pass with a debug build and I have also compiled the input file (using llvm-gcc) with the -g flag. Given below is the exact output. (gdb) break llvm::PassManager::run Breakpoint 1 at 0x86be87c: file

I tried to run gdb in linux with emacs But could not even run a simple example in the writing extensions tutorial. The execution history is as follows. Gdb worked fine for other debugging such as C++ codes. Thanks Han I started R at echo of emacs by typing (also tried other methods mentioned in the tutorial both in emacs and xterm.) M-x gdb ==> R -d gdb (gdb) run Starting program: