From: Andreas Schwab <schwab@linux-m68k.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 1/2+7.6] /proc/PID/smaps: filename fix
Date: Sun, 31 Mar 2013 17:43:00 -0000 [thread overview]
Message-ID: <m21uay3qex.fsf@igel.home> (raw)
In-Reply-To: <20130329195301.GA3502@host2.jankratochvil.net> (Jan Kratochvil's message of "Fri, 29 Mar 2013 20:53:01 +0100")
Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> currently GDB complains:
> warning: Error parsing {s,}maps file '[heap]'
> warning: Error parsing {s,}maps file '/usr/lib64/libc-2.17.so'
>
> which is sure incorrect, it should have been:
> warning: Error parsing {s,}maps file '/proc/30100/smaps'
> warning: Error parsing {s,}maps file '/proc/30100/smaps'
Which mean you'll no longer know what's wrong with it.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2013-03-29 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-31 17:43 Jan Kratochvil
2013-03-31 17:43 ` Andreas Schwab [this message]
[not found] ` <20130329202737.GA6075@host2.jankratochvil.net>
2013-04-05 19:51 ` Pedro Alves
2013-04-05 20:20 ` [commit+7.6] " Jan Kratochvil
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=m21uay3qex.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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