x/i 0x204c5ac. seg fault

[Dave Korn]

On 28 April 2006 16:18, Daniel Jacobowitz wrote:

> On Fri, Apr 28, 2006 at 05:10:54PM +0200, Andreas Schwab wrote:
>> Daniel Jacobowitz <drow@false.org> writes:
>> 
>>> 2.  The system sscanf in glibc apparently rejects hex float.
>> 
>> A valid hex float constant always contains a 'p' or 'P'.
> 
> OK, so it's 100% GDB's fault then.  Thanks for the correction.
> This should probably be an error.

  And indeed perhaps the fact that newlib apparently /doesn't/ return an error
should be considered a bug too.  Or perhaps newlib doesn't support hex floats
and regards it as a hex integer constant and just stops scanning at the
period, assuming it's part of the next field.  I'll try and take a look
through the newlib source at the weekend unless someone on the newlib list
[Cc'd in] comments that this is intended behaviour.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....