As I understand what is going on, it is definitely a vulnerability to have a pointer to a fixed string being handed out as if it is a variable. You can get rid of it by the flag for no write strings, which is one of the options. But I don't know enough about the problem to say which of the choices it should be, and you don't seem to either.
On Wed, Nov 4, 2009 at 4:56 AM, Argent Stonecutter <[email protected]> wrote: > On 2009-11-03, at 12:30, Lillian Yiyuan wrote: >> That produces the same error. I suppose the question is whether the >> variables should be const char to begin with, but I don't know enough >> about them to know whether they are modified, and thus don't want to >> change the definition. The error also shows up in the mac-updater. > > If this is an _error_ and not a warning, then that's a compiler > problem, or a command line problem. I suspect the latter. > > It's better to leave the warning in place for someone to track down > and fix properly. > > _______________________________________________ > Policies and (un)subscribe information available here: > http://wiki.secondlife.com/wiki/SLDev > Please read the policies before posting to keep unmoderated posting privileges > _______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/SLDev Please read the policies before posting to keep unmoderated posting privileges
