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] Add proper error message instead of gdb_assert

From: Daniel Jacobowitz <drow at false dot org>
To: Markus Deuling <deuling at de dot ibm dot com>
Cc: gdb-patches at sourceware dot org, Michael Snyder <msnyder at specifix dot com>, Mark Kettenis <mark dot kettenis at xs4all dot nl>, uweigand at de dot ibm dot com
Date: Mon, 3 Mar 2008 16:17:05 -0500
Subject: Re: [patch] Add proper error message instead of gdb_assert
References: <47CC5332.3020700@de.ibm.com> <200803031955.m23Jt7cj019540@brahms.sibelius.xs4all.nl> <1204576131.19253.582.camel@localhost.localdomain> <20080303203858.GA22316@caradoc.them.org> <47CC6990.7080400@de.ibm.com>

On Mon, Mar 03, 2008 at 10:11:44PM +0100, Markus Deuling wrote:
> What about the attached patch? It gives an error message in value_assign if you try to
> access lval_register < 0. I guess this is much better for the user than a crashed GDB session.
>
> What do you think ?

No.  Both of these are internal errors in GDB.  The internal error
prompt already gives you the option to keep going if you want to.

-- 
Daniel Jacobowitz
CodeSourcery

References:
- [patch] Add proper error message instead of gdb_assert
  - From: Markus Deuling
- Re: [patch] Add proper error message instead of gdb_assert
  - From: Mark Kettenis
- Re: [patch] Add proper error message instead of gdb_assert
  - From: Michael Snyder
- Re: [patch] Add proper error message instead of gdb_assert
  - From: Daniel Jacobowitz
- Re: [patch] Add proper error message instead of gdb_assert
  - From: Markus Deuling

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