public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Brad Aisa <baisa@colorado.edu>
To: gdb@sourceware.org
Subject: Re: GDB fails from Kdbg
Date: Wed, 12 Oct 2005 19:58:00 -0000	[thread overview]
Message-ID: <200510121358.09086.baisa@colorado.edu> (raw)
In-Reply-To: <20051012185310.GA28855@nevyn.them.org>

Did you follow the series of commands below, or just go:
gdb clipview

Because the latter works -- it is the sequence below that fails, and 
that is the sequence emitted by Kdbg when it loads an executable.

On Wednesday 12 October 2005 12:53 pm, Daniel Jacobowitz wrote:
> On Wed, Oct 12, 2005 at 12:29:24PM -0600, Brad Aisa wrote:
> > Here is the instructions someone was given from the kdbg people
> > who were trying to debug this, which I followed -- this is
> > basically the commands issued by Kdbg, as copied from a log of
> > launching with Kdbg:
> >
> > gdb
> > set editing off
> >  set confirm off
> >  set print static-members off
> >  set print asm-demangle on
> >  define kdbg__alllocals
> >  info locals
> >  info args
> >  end
> >  set prompt (kdbg)
> >  file "clipview"
> >  set args
> >  info breakpoints
> >  info line main
> >
> > At the "info line main" point I got:
> > Segmentation fault
>
> The binary you send me does not crash at this point in any version
> of GDB I tried.  Have you build GDB CVS or 6.3 from source to try,
> rather than using the preinstalled packages on your system?

-- 
Brad Aisa <baisa at colorado dot edu>
Professional Research Assistant
Department of Psychology
University of Colorado - Boulder

  reply	other threads:[~2005-10-12 19:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-12 17:05 Brad Aisa
2005-10-12 17:41 ` Daniel Jacobowitz
2005-10-12 18:29   ` Brad Aisa
2005-10-12 18:53     ` Daniel Jacobowitz
2005-10-12 19:58       ` Brad Aisa [this message]
2005-10-12 20:01         ` Daniel Jacobowitz
2005-10-12 22:03       ` Brad Aisa
2005-10-13  3:18         ` Daniel Jacobowitz

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=200510121358.09086.baisa@colorado.edu \
    --to=baisa@colorado.edu \
    --cc=gdb@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).