Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Rich Coe <Richard.Coe@med.ge.com>
Cc: "H. J. Lu" <hjl@lucon.org>, gdb@sources.redhat.com
Subject: Re: no stack trace with 2.6.11 and gdb 6.3
Date: Fri, 10 Jun 2005 19:37:00 -0000	[thread overview]
Message-ID: <20050610193720.GA24094@nevyn.them.org> (raw)
In-Reply-To: <20050610142058.671c9987@godzilla>

On Fri, Jun 10, 2005 at 02:20:58PM -0500, Rich Coe wrote:
> Yes, after I manually run
>     'add-symbol-file-from-memory 0xffffe000'
> I can get a valid traceback.  
> 
> Why doesn't this just work like gdb-6.0 on 2.6.7 ?

Your GDB 6.0 was also patched by Red Hat; again, you would have to ask
them.

> Why does this command run automatically when debugging with gdb from the
> command line but when attaching to an already running process ?

Because it's different code that detects the new program.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-06-10 19:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-10 18:00 Rich Coe
2005-06-10 18:11 ` Daniel Jacobowitz
2005-06-10 19:02   ` Rich Coe
2005-06-10 19:05     ` H. J. Lu
2005-06-10 19:09       ` Christopher Faylor
2005-06-10 19:10       ` Daniel Jacobowitz
2005-06-10 19:23       ` Rich Coe
2005-06-10 19:37         ` Daniel Jacobowitz [this message]
2005-06-10 21:17           ` richard.coe
2005-06-11  0:51             ` Daniel Jacobowitz
2005-06-11  2:21               ` H. J. Lu
2005-06-13 15:19                 ` Rich Coe
2005-06-13 15:26                   ` H. J. Lu
2005-06-13 15:36                     ` Rich Coe
2005-06-13 20:13                       ` H. J. Lu
2005-06-13 20:16                         ` Daniel Jacobowitz
2005-06-13 20:30                           ` H. J. Lu
2005-06-13 20:33                             ` Daniel Jacobowitz
2005-06-13 20:36                     ` Rich Coe
2005-06-13 20:43                       ` 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=20050610193720.GA24094@nevyn.them.org \
    --to=drow@false.org \
    --cc=Richard.Coe@med.ge.com \
    --cc=gdb@sources.redhat.com \
    --cc=hjl@lucon.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