From: Andrew Cagney <ac131313@cygnus.com>
To: John S Kallal <jskallal@home.com>,
Adam Mirowski <mir@solfege.France.Sun.COM>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH} Minor bug fix in arch-utils.c
Date: Thu, 10 May 2001 08:33:00 -0000 [thread overview]
Message-ID: <3AF9A729.6090207@cygnus.com> (raw)
In-Reply-To: <000701c0cea9$7b18ed80$6401a8c0@cn986452a>
> The following is a one line patch to
> end a segmentation fault when the
> command 'info architecture' is used
> on GDB running on a SUSE-7.0 Linux
> system.
>
>
> 2001-04-26 John S Kallal <jskallal@home.com>
>
> * arch-utils.c/info_architecture: Remove 2nd
> pointer list update to correctly follow
> linked list.
Yes, I've seen this patch twice now. While an obvious fix, I'm going to
check in the attached. The ``info architecture'' command can simply be
deleted.
Andrew
next parent reply other threads:[~2001-05-10 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000701c0cea9$7b18ed80$6401a8c0@cn986452a>
2001-05-10 8:33 ` Andrew Cagney [this message]
2001-05-10 9:26 ` Fernando Nasser
2001-05-10 10:27 ` Andrew Cagney
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=3AF9A729.6090207@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jskallal@home.com \
--cc=mir@solfege.France.Sun.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