Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@kealia.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: correctly place new inclusions in includer's list
Date: Mon, 22 Sep 2003 20:11:00 -0000	[thread overview]
Message-ID: <yf2pths60si.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <vt2llsgehpf.fsf@zenia.home> (Jim Blandy's message of "22 Sep 2003 14:39:08 -0500")

On 22 Sep 2003 14:39:08 -0500, Jim Blandy <jimb@redhat.com> said:
> David Carlton <carlton@kealia.com> writes:

>> I've seen macrotab seg faults intermittently over the last few
>> months; I've been too lazy to track them down (they're hard to
>> reproduce, and I didn't know if it was something weird about my
>> branch or a bug in mainline), but if this patch might fix them, and
>> if it's as trivial as it seems, then putting it in 6.0 makes sense
>> to me.

> It's hard to see how this would fix any seg faults.  It just fixes
> where in the list the traversal stops; but no matter where it stops,
> the other loop conditions ensure that it stops in a structurally
> valid state.

> So I'd say the segfaults you've seen don't weigh for or against.

Oh well.  I'll keep my eye out for them (I haven't seen one in a
little while) and see if I can find a way to reproduce them regularly
(or fix them?), then.

David Carlton
carlton@kealia.com


      reply	other threads:[~2003-09-22 20:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-19 21:50 Jim Blandy
2003-09-22 18:00 ` Jim Blandy
2003-09-22 18:06   ` David Carlton
2003-09-22 18:28     ` Andrew Cagney
2003-09-22 22:28       ` Jim Blandy
2003-09-22 19:42     ` Jim Blandy
2003-09-22 20:11       ` David Carlton [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=yf2pths60si.fsf@hawaii.kealia.com \
    --to=carlton@kealia.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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