From: "H. J. Lu" <hjl@lucon.org>
To: Rich Coe <Richard.Coe@med.ge.com>, gdb@sources.redhat.com
Subject: Re: no stack trace with 2.6.11 and gdb 6.3
Date: Mon, 13 Jun 2005 20:30:00 -0000 [thread overview]
Message-ID: <20050613203046.GA15935@lucon.org> (raw)
In-Reply-To: <20050613201635.GA4684@nevyn.them.org>
On Mon, Jun 13, 2005 at 04:16:35PM -0400, Daniel Jacobowitz wrote:
> On Mon, Jun 13, 2005 at 01:13:50PM -0700, H. J. Lu wrote:
> > You also need this patch for gdb 6.3.
> >
> >
> > H.J.
> > --- gdb/inftarg.c.attach 2004-11-11 16:46:57.000000000 -0800
> > +++ gdb/inftarg.c 2005-06-13 13:07:14.000000000 -0700
> > @@ -211,6 +211,10 @@ child_attach (char *args, int from_tty)
> >
> > inferior_ptid = pid_to_ptid (pid);
> > push_target (&deprecated_child_ops);
> > +
> > + /* Do this first, before anything has had a chance to query the
> > + inferiors symbol table or similar. */
> > + observer_notify_inferior_created (¤t_target, from_tty);
> > }
> >
> > #if !defined(CHILD_POST_ATTACH)
> >
>
> Which is already in GDB CVS, which Rich has already said did not work
> for him.
>
He was using gdb 6.3, not gdb head. See
http://sources.redhat.com/ml/gdb/2005-06/msg00114.html
H.J.
next prev parent reply other threads:[~2005-06-13 20:30 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
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 [this message]
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=20050613203046.GA15935@lucon.org \
--to=hjl@lucon.org \
--cc=Richard.Coe@med.ge.com \
--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