From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix crash on NULL rl_prompt
Date: Tue, 30 Mar 2010 15:57:00 -0000 [thread overview]
Message-ID: <m37hotztsn.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100329234026.GA23895@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Tue, 30 Mar 2010 01:40:26 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> BTW don't you think xstrdup (NULL) should == NULL? Like xmalloc
Jan> (0) == NULL.
I personally don't care either way. If you want to do it, that is fine
by me.
Jan> 2010-03-30 Jan Kratochvil <jan.kratochvil@redhat.com>
Jan> * tui/tui-io.c (tui_prep_terminal): Permit NULL rl_prompt.
Ok.
Tom
next prev parent reply other threads:[~2010-03-30 15:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 23:40 Jan Kratochvil
2010-03-30 15:57 ` Tom Tromey [this message]
2010-03-30 16:12 ` Pedro Alves
2010-03-30 16:23 ` Tom Tromey
2010-03-30 16:41 ` Pedro Alves
2010-03-30 17:05 ` Jan Kratochvil
2010-03-30 17:13 ` Tom Tromey
2010-03-30 17:25 ` Pedro Alves
2010-03-30 17:29 ` Jan Kratochvil
2010-03-30 17:55 ` Pedro Alves
2010-03-31 21:27 ` [cancel] " Jan Kratochvil
2010-03-30 17:31 ` Tom Tromey
2010-03-30 20:50 ` Pedro Alves
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=m37hotztsn.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--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