From: Jim Blandy <jimb@cygnus.com>
To: dhawkins@dhawkins.dsl.frii.com
Cc: gdb-patches@cygnus.com
Subject: Re: bug in gdb
Date: Mon, 19 Apr 1999 09:44:00 -0000 [thread overview]
Message-ID: <npd810wqur.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <87n206kfz7.fsf@dhawkins.dsl.frii.com>
> Found a bug in gdb. This seems to be the correct fix. (I give the
> code unconditionally to the FSF for what ever they wish to do with
> it..., yadda, yadda, yadda). It does not seem to warrant much
> fanfare.
For a change this small, we don't need a copyright assignment. It's
not large enough to be copyrightable.
> Changelog entry:
> Fixed a bug where the typevec_size was not being reset to zero after
> the typevec itself had been reset.
The fix looks reasonable, but can you give me an identifier to
demangle that makes the bug appear?
From shebs@cygnus.com Mon Apr 19 14:08:00 1999
From: Stan Shebs <shebs@cygnus.com>
To: robertl@sco.com
Cc: gdb-patches@cygnus.com
Subject: Re: GDB 4.18 on SVR5: missed it by a hair
Date: Mon, 19 Apr 1999 14:08:00 -0000
Message-id: <199904192047.NAA18881@andros.cygnus.com>
References: <19990415225503.A10488@rjlhome.sco.com>
X-SW-Source: 1999-04/msg00040.html
Content-length: 414
Date: Thu, 15 Apr 1999 22:55:03 -0500
From: Robert Lipe <robertl@sco.com>
The round of optimizations we performed on configure.host didn't
make it to configure.tgt. So SVR5 gets detected as SVR4.0 so it
gets /proc filesystem handling silently wrong. :-(
Argh! The change is in the trunk, but I forget to add it to the 4.18
branch also. Well, there's a third patch for 4.18.1...
Stan
WARNING: multiple messages have this Message-ID
From: Jim Blandy <jimb@cygnus.com>
To: dhawkins@dhawkins.dsl.frii.com
Cc: gdb-patches@cygnus.com
Subject: Re: bug in gdb
Date: Mon, 19 Apr 1999 08:52:00 -0000 [thread overview]
Message-ID: <npd810wqur.fsf@zwingli.cygnus.com> (raw)
Message-ID: <19990419085200.e1zTX2ksov1SfrALg4X5WuzIxPpUm2vxBYx6XErmDrE@z> (raw)
In-Reply-To: <87n206kfz7.fsf@dhawkins.dsl.frii.com>
> Found a bug in gdb. This seems to be the correct fix. (I give the
> code unconditionally to the FSF for what ever they wish to do with
> it..., yadda, yadda, yadda). It does not seem to warrant much
> fanfare.
For a change this small, we don't need a copyright assignment. It's
not large enough to be copyrightable.
> Changelog entry:
> Fixed a bug where the typevec_size was not being reset to zero after
> the typevec itself had been reset.
The fix looks reasonable, but can you give me an identifier to
demangle that makes the bug appear?
next prev parent reply other threads:[~1999-04-19 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-17 16:05 dhawkins
1999-04-19 9:44 ` Jim Blandy [this message]
1999-04-19 8:52 ` Jim Blandy
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=npd810wqur.fsf@zwingli.cygnus.com \
--to=jimb@cygnus.com \
--cc=dhawkins@dhawkins.dsl.frii.com \
--cc=gdb-patches@cygnus.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