This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch] Fix crash on NULL rl_prompt

From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
To: Pedro Alves <pedro at codesourcery dot com>
Cc: tromey at redhat dot com, gdb-patches at sourceware dot org
Date: Tue, 30 Mar 2010 19:04:57 +0200
Subject: Re: [patch] Fix crash on NULL rl_prompt
References: <20100329234026.GA23895@host0.dyn.jankratochvil.net> <201003301712.20874.pedro@codesourcery.com> <m3eij1ye1x.fsf@fleche.redhat.com> <201003301741.20844.pedro@codesourcery.com>

On Tue, 30 Mar 2010 18:41:20 +0200, Pedro Alves wrote:
> But, how did rl_prompt end up NULL in the first place?

I do not know.  I have spent some time trying to reproduce it reading the
source but gave up after some reasonable time.  Bugreport comes from an
automated crash reporter (ABRT) where the person only sometimes can/gives more
info.  Asked now for a reproducer.

> Was GDB running in batch/non-tty stdin, "set editing off", with readline not
> setup at all, and tried to enable the TUI/curses anyway?

Tried also this one with no luck (=with no crash).
	gdb -nx -ex 'set editing off' -ex 'tui reg general';echo $?

> That's what I meant by masking out a bug.

An existing bug a user cannot notice is ... no longer a bug, isn't it?

Thanks,
Jan

Follow-Ups:
- Re: [patch] Fix crash on NULL rl_prompt
  - From: Tom Tromey
- Re: [patch] Fix crash on NULL rl_prompt
  - From: Pedro Alves

References:
- [patch] Fix crash on NULL rl_prompt
  - From: Jan Kratochvil
- Re: [patch] Fix crash on NULL rl_prompt
  - From: Pedro Alves
- Re: [patch] Fix crash on NULL rl_prompt
  - From: Tom Tromey
- Re: [patch] Fix crash on NULL rl_prompt
  - From: Pedro Alves

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]