public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "hicham at mouline dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/11964] New: support for debugging multithreaded openmp Date: Wed, 01 Sep 2010 03:47:00 -0000 [thread overview] Message-ID: <20100901034743.11964.hicham@mouline.org> (raw) Hello, While debugging this program https://computing.llnl.gov/tutorials/openMP/samples/C/omp_hello.c under emacs/GUD with gdb, putting a breakpoint inside the parallel region, line 30, triggers a stop at that point. However, stepping over generates this error "Cannot find bounds of current function", when the cursor hits line 22 (the pragma line) The program was built with gcc (GCC) 4.4.4 20100630 (Red Hat 4.4.4-10), and its associated libgomp library. A fix is proposed by jan.kratochvil@redhat.com though I'm not sure it's related to this particular point: http://cvs.fedoraproject.org/viewvc/rpms/gdb/devel/gdb-bz533176-fortran-omp- step.patch?content-type=text%2Fplain&view=co regards, -- Summary: support for debugging multithreaded openmp Product: gdb Version: 7.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb AssignedTo: unassigned at sourceware dot org ReportedBy: hicham at mouline dot org CC: gdb-prs at sourceware dot org GCC build triplet: x86_64-redhat-linux-gnu GCC host triplet: Linux 2.6.33.3 x86_64 GCC target triplet: 7.1-33.fc13 http://sourceware.org/bugzilla/show_bug.cgi?id=11964 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2010-09-01 3:47 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-09-01 3:47 hicham at mouline dot org [this message] 2010-09-01 3:55 ` [Bug gdb/11964] " hicham at mouline dot org 2010-09-02 21:20 ` jan dot kratochvil at redhat dot com 2010-09-03 6:14 ` jan dot kratochvil at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20100901034743.11964.hicham@mouline.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).