From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Snyder <msnyder@cygnus.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Daniel Berlin <dan@cgsoftware.com>, gdb-patches@sources.redhat.com
Subject: Re: Simple but crucial bug fix to gdb
Date: Fri, 01 Jun 2001 10:01:00 -0000
Message-id: <3B17CA59.6C83B926@cygnus.com>
References: <3.0.5.32.20010530142745.01470ec0@pophost.pdxuxbre.lmc.com> <20010530173650.A21397@redhat.com> <3B15711D.BEA4B77E@cygnus.com> <npvgmimcih.fsf@zwingli.cygnus.com> <3B1638A2.79AE4BCF@redhat.com> <npelt5me4f.fsf@zwingli.cygnus.com> <20010531194656.A27403@redhat.com> <87ofs9hw29.fsf@dynamic-addr-83-177.resnet.rochester.edu> <o57kywdhvp.fsf@touchme.toronto.redhat.com>
X-SW-Source: 2001-06/msg00005.html

"Frank Ch. Eigler" wrote:
> 
> Daniel Berlin <dan@cgsoftware.com> writes:
> 
> : [...]
> : However, we should *never* see a case where pst is NULL, and
> : textlow_not_set is 1, at the point we see a function.
> : [...]
> 
> Would a gdb_assert() to this effect satisfy all sides?

gdb_assert causes an abort if the conditional fails.
I generally think it's better if the debugger doesn't abort
(unles it's believed to be in an unrecoverable state).