public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Kevin Powell <KPowell@sirf.com>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: RE: Building Insight snapshot on CygWin?
Date: Tue, 24 Jun 2003 02:00:00 -0000	[thread overview]
Message-ID: <1056420563.1574.90.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <C2190B0C813D9E49BBAA0293F900204301C8B22E@sjexchange.sirf.com>

On Mon, 2003-06-23 at 18:45, Kevin Powell wrote:
> As promised, here is the result of using an unoptimized insight/gdb.  BTW, thanks for the tip on turning off the optimizations.  At least now I can get a usable (not to me, but maybe to others) backtrace.
>
> The executive summary is that the unoptimized gdb behaves a bit better than my first attempt.  At least now I can set a breakpoint and run to it. However, the first time I try to step, gdb crashes with the same segfault as before.  And, to answer your question from the last email, it really is gdb that is crashing -- the target program runs fine both under the distributed gdb and outside of the debugger.  And, now I know the reason why it crashes:  
> 

This is perfect! Insight isn't even in the backtrace! :-)

Please send/forward your excellent message to the gdb list. They've been
churning the dwarf2 readers for a little while now, and it looks like
you've either uncovered a bug or are missing a recent patch.

In either case, the whizzes on the gdb list (gdb at sources dot redhat
dot com) will be able to guide you better.

Keith

PS. Your message is perfect! An example session and a backtrace! How
refreshing!


  reply	other threads:[~2003-06-24  2:00 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-24  1:46 Kevin Powell
2003-06-24  2:00 ` Keith Seitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-07 19:44 John Lowen
2003-07-07 19:57 ` Keith Seitz
2003-06-24  0:14 Kevin Powell
2003-06-24  1:09 ` Keith Seitz
2003-06-23 23:18 Kevin Powell
2003-06-23 23:31 ` Keith Seitz
2003-06-09 15:53 Schumacher, Gordon
2003-06-09 17:53 ` Keith Seitz
2003-06-09  9:28 vadraj kulkarni
2003-06-11 20:11 ` Keith Seitz
2003-06-03 20:02 Schumacher, Gordon
2003-06-06 20:45 ` Keith Seitz
2003-05-21 20:47 Schumacher, Gordon
2003-05-27 18:30 ` Keith Seitz
2003-05-21 17:18 Schumacher, Gordon
2003-05-21 17:19 ` Keith Seitz
2003-05-21 18:55   ` Keith Seitz
2003-05-21 19:02     ` Martin M. Hunt
2003-05-21 21:37       ` Keith Seitz
2003-05-21 23:08         ` Keith Seitz
2003-05-21 23:49           ` Andrew Cagney
2003-05-21 16:54 Schumacher, Gordon
2003-05-21 17:02 ` Keith Seitz
2003-05-21 19:58 ` Martin M. Hunt

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=1056420563.1574.90.camel@lindt.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=KPowell@sirf.com \
    --cc=insight@sources.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).