public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/15257] !!!Bug gdb needed to change to intel64 idb to work!!!
Date: Fri, 08 Mar 2013 21:31:00 -0000	[thread overview]
Message-ID: <bug-15257-4717-jZJQh3SXer@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15257-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15257

Tom Tromey <tromey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
                 CC|                            |tromey at redhat dot com

--- Comment #1 from Tom Tromey <tromey at redhat dot com> 2013-03-08 21:31:07 UTC ---
(In reply to comment #0)

> /usr/local/netbeans-7.2.1/ide/bin/nativeexecution/dorun.sh: line 33: 7673
> Segmentation fault sh "${SHFILE}"


There isn't enough information in this report for us to
know what is going wrong.

I don't know what dorun.sh does.  I didn't see any invocation
of gdb, or any gdb output, in the bug report.

If gdb is crashing, then a good starting point is to run gdb
in the terminal and reproduce the crash there.
If you can do this, then the next step is getting a stack
trace from gdb.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  reply	other threads:[~2013-03-08 21:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08 17:52 [Bug c++/15257] New: " aleksandar.jelic30 at gmail dot com
2013-03-08 21:31 ` tromey at redhat dot com [this message]
2013-03-10 16:15 ` [Bug c++/15257] " aleksandar.jelic30 at gmail dot com
2013-05-15 21:58 ` dje at google dot com
2014-09-12 23:11 ` sergiodj 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=bug-15257-4717-jZJQh3SXer@http.sourceware.org/bugzilla/ \
    --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: link
Be 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).