From: Bahadir Balban <bbalban@b-labs.com>
To: keiths@redhat.com
Cc: insight@sourceware.org
Subject: Re: Next Release Status
Date: Thu, 15 Dec 2011 14:38:00 -0000 [thread overview]
Message-ID: <1323959867.12606.3.camel@bbalban-desktop> (raw)
In-Reply-To: <1323958948.4820.8.camel@bbalban-desktop>
On Thu, 2011-12-15 at 16:22 +0200, Bahadir Balban wrote:
> Hi Keith/Christopher,
>
>
> > On 11/08/2011 04:16 PM, Christopher Faylor wrote:
> > Actually, I've been able to build this without much effort. I just
> > don't like the current state of affairs wrt cygwin tcl/tk and insight so
> > I haven't been motivated to make a release.
>
> Would you please share instructions on how to build Insight against
> GDB-7.x?
>
> We are using it in fashion of ICE debugging with QEMU and gdb-6.8 seem
> to have debug issues with recent toolchains. I would appreciate a new
> release.
>
Is it possible to compile Insight as detached from a specific GDB
version? In DDD ddd --gdb --debugger option specifies the GDB version.
This is the way we confirmed that insight's gdb and latest GDB differed
in the way they step through our latest compiled code. Insight is
skipping certain function bodies as if they were inlined.
Thanks,
Bahadir
next prev parent reply other threads:[~2011-12-15 14:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 14:22 Bahadir Balban
2011-12-15 14:38 ` Bahadir Balban [this message]
2011-12-17 18:17 ` Keith Seitz
2011-12-18 18:37 ` Bahadir Balban
2011-12-19 17:41 ` Keith Seitz
2011-12-20 12:18 ` Bahadir Balban
2011-12-17 18:14 ` Keith Seitz
-- strict thread matches above, loose matches on Subject: below --
2011-11-08 17:51 Keith Seitz
2011-11-08 22:14 ` Matthias Andree
2011-11-09 0:17 ` Christopher Faylor
2011-11-09 23:32 ` Keith Seitz
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=1323959867.12606.3.camel@bbalban-desktop \
--to=bbalban@b-labs.com \
--cc=insight@sourceware.org \
--cc=keiths@redhat.com \
/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).