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

I downloaded the cvs snapshot gdb-6.3.50.20050607, built, and ran gdb 
and the problem still persists.

What next ?

On Fri, 10 Jun 2005 14:11:40 -0400
Daniel Jacobowitz <drow@false.org> wrote:
> On Fri, Jun 10, 2005 at 12:58:55PM -0500, Rich Coe wrote:
> > I have been investigating a problem we found here, which initially
> > exactly matched the problem reported here:
> > 
> >     https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=146087
> > 
> >     1. Start a 32-bit app on a x86_64 system
> >     2. attach with gdb
> >     3. backtrace starting in a system call doesn't work
> > 
> > Our versions:
> >     kernel: 2.6.11.11
> >     gdb: 6.3.0.0-1.21
> 
> This is presumably a bug in that Red Hat-supplied version of GDB.  We
> can't help you with it on this list; if you can reproduce it with the
> version of GDB in CVS, please let us know, otherwise you should discuss
> it with Red Hat.
> 
> Code was added sometime last year to handle loading the vDSO on attach.
> 
> -- 
> Daniel Jacobowitz
> CodeSourcery, LLC
> 


-- 
Rich Coe		richard.coe@med.ge.com
General Electric Healthcare Technologies
Global Software Platforms, Computer Technology Team


  reply	other threads:[~2005-06-10 19:02 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 [this message]
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
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=20050610135940.23bd015c@godzilla \
    --to=richard.coe@med.ge.com \
    --cc=drow@false.org \
    --cc=gdb@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