public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb-patches@sourceware.org, "Maciej W. Rozycki" <macro@codesourcery.com>
Subject: Re: [RFA]corelow.c: Add tid to add_to_thread_list
Date: Mon, 09 Aug 2010 14:48:00 -0000	[thread overview]
Message-ID: <201008091547.51389.pedro@codesourcery.com> (raw)
In-Reply-To: <AANLkTimV=tis9-KCskjmNDvHuityj4v_-2OfG7g8nEHd@mail.gmail.com>

On Monday 09 August 2010 03:28:23, Hui Zhu wrote:

> It work on my part got:
> 
> Reading symbols from /home/teawater/tmp/vmlinux...done.
> [New process 1]
> [New process 1]
> [New process 1]
> [New LWP 2731]
> #0  0xffffffff8020b037 in __sti_mwait () at include2/asm/processor.h:719
> 719	include2/asm/processor.h: No such file or directory.
> 	in include2/asm/processor.h
> (gdb) info threads
>   4 LWP 2731  crash_setup_regs (regs=0x0) at include2/asm/kexec.h:155
> * 3 process 1  0xffffffff8020b037 in __sti_mwait () at
> include2/asm/processor.h:719

Thanks for confirming.

> Looks this is a fit way without change libbfd.

IMO, I'd still be better to teach bfd about these cores as I
suggested before, but it doesn't itch me enough to go
fix it myself.  ;-)

-- 
Pedro Alves

      reply	other threads:[~2010-08-09 14:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03  8:49 Hui Zhu
2010-08-05 18:44 ` Tom Tromey
2010-08-06  2:56   ` Hui Zhu
2010-08-06  9:57     ` Pedro Alves
2010-08-06 16:48       ` Hui Zhu
2010-08-06 17:18         ` Pedro Alves
2010-08-06 20:06           ` Pedro Alves
2010-08-06 20:50             ` Maciej W. Rozycki
2010-08-09  2:28             ` Hui Zhu
2010-08-09 14:48               ` Pedro Alves [this message]

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=201008091547.51389.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@codesourcery.com \
    --cc=teawater@gmail.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).