Re: bug in visual studio .net 2003 - breakpoints and memcpy
- From: "Don Burn" <burn@xxxxxxxxxxxxxxxx>
- Date: Sun, 17 Jul 2005 07:44:52 -0400
Ok, this is from the era when the Open Group took over Posix. I had been on
the POSIX committee in the early 1990's and sure didn't remember it. Of
course some of us believe that after the take over POSIX was never the same.
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
"Eugene Gershnik" <gershnik@xxxxxxxxxxx> wrote in message
news:u6zmDEoiFHA.572@xxxxxxxxxxxxxxxxxxxxxxx
> Don Burn wrote:
>> Sorry, but I am pretty sure POSIX does not require this. I used to
>> work for a firm with a machine with seperate instruction and data
>> spaces, and while the memory is old, I remember reviewing the system
>> for POSIX compliance. It was because of seperate I&D space systems
>> that this was not part of the C language standard.
>
> See
>
> http://www.opengroup.org/onlinepubs/009695399/functions/dlsym.html
>
> and note the return value of this function. On the same page there is a
> "rationale" section that talk about this particular issue.
>
>
> --
> Eugene
> http://www.gershnik.com
>
>
.
- References:
- bug in visual studio .net 2003 - breakpoints and memcpy
- From: Gareth Haslip
- Re: bug in visual studio .net 2003 - breakpoints and memcpy
- From: Alexander Grigoriev
- Re: bug in visual studio .net 2003 - breakpoints and memcpy
- From: Eugene Gershnik
- Re: bug in visual studio .net 2003 - breakpoints and memcpy
- From: Don Burn
- Re: bug in visual studio .net 2003 - breakpoints and memcpy
- From: Eugene Gershnik
- bug in visual studio .net 2003 - breakpoints and memcpy
- Prev by Date: Canonical names for kernel objects
- Next by Date: Re: bug in visual studio .net 2003 - breakpoints and memcpy
- Previous by thread: Re: bug in visual studio .net 2003 - breakpoints and memcpy
- Next by thread: Re: bug in visual studio .net 2003 - breakpoints and memcpy
- Index(es):
Relevant Pages
|
Loading