GNU bug report logs - #40671
[DOC] modify literal objects

Previous Next

Full log

View this message in rfc822 format

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: ke.vigouroux <at> laposte.net, eggert <at> cs.ucla.edu, 40671 <at> debbugs.gnu.org, michael_heerdegen <at> web.de, mattiase <at> acm.org, rms <at> gnu.org
Subject: bug#40671: [DOC] modify literal objects
Date: Sun, 26 Apr 2020 21:53:05 +0300

On 26.04.2020 21:41, Eli Zaretskii wrote:
>> Cc: ke.vigouroux <at> laposte.net, eggert <at> cs.ucla.edu, 40671 <at> debbugs.gnu.org,
>>   michael_heerdegen <at> web.de, mattiase <at> acm.org, rms <at> gnu.org
>> From: Dmitry Gutov <dgutov <at> yandex.ru>
>> Date: Sun, 26 Apr 2020 21:32:45 +0300
>>
>> My point is, that program is using the same instrument as this one,
>> which *will* blow up at runtime.
> 
> No, it isn't the same instrument.  Your program constructs a function
> call using address that has no valid instructions.  Paul's program
> does nothing like that, it just attempts to write to a data address
> which may or may not be in write-protected storage.  So your program
> will always blow up, whereas the other one will only blow up if the
> memory is write-protected.

I was imprecise. The program is doing a different thing.

But the programmer is using the same instrument in both cases to make it 
compile.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.