Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

80%
+6 −0
Q&A Is it undefined behaviour to just make a pointer point outside boundaries of an array without dereferencing it?

I have heard that it is undefined behaviour to make a pointer point outside boundaries of an array even without dereferencing it. Can that really be true? Consider this code: int main(void) { ...

2 answers  ·  posted 4y ago by klutt‭  ·  last activity 4y ago by hkotsubo‭

#3: Post edited by user avatar klutt‭ · 2020-08-19T10:49:23Z (over 4 years ago)
  • I have heard that it is undefined behaviour to make a pointer point outside boundaries of an array even without dereferencing it. Can that really be true? Consider this code:
  • int main(void)
  • {
  • char arr[10];
  • char *ptr = arr[-1];
  • char c = *ptr;
  • }
  • The line `char c = *ptr` is obviously bad, because it's accessing out of bounds. But I heard something that even the second line invokes undefined behaviour? Is this true? What does the standard say?
  • I have heard that it is undefined behaviour to make a pointer point outside boundaries of an array even without dereferencing it. Can that really be true? Consider this code:
  • int main(void)
  • {
  • char arr[10];
  • char *ptr = &arr[-1];
  • char c = *ptr;
  • }
  • The line `char c = *ptr` is obviously bad, because it's accessing out of bounds. But I heard something that even the second line `char *ptr = &arr[-1]` invokes undefined behaviour? Is this true? What does the standard say?
#2: Post edited by user avatar klutt‭ · 2020-08-18T09:36:25Z (over 4 years ago)
  • I have heard that it is undefined behaviour to make a pointer point outside boundaries of an array even without dereferencing it. Can that really be true? Consider this code:
  • char arr[10];
  • char *ptr = arr[-1];
  • char c = *ptr;
  • The third line is obviously bad, because it's accessing out of bounds. But I heard something that even the second line invokes undefined behaviour? Is this true? What does the standard say?
  • I have heard that it is undefined behaviour to make a pointer point outside boundaries of an array even without dereferencing it. Can that really be true? Consider this code:
  • int main(void)
  • {
  • char arr[10];
  • char *ptr = arr[-1];
  • char c = *ptr;
  • }
  • The line `char c = *ptr` is obviously bad, because it's accessing out of bounds. But I heard something that even the second line invokes undefined behaviour? Is this true? What does the standard say?
#1: Initial revision by user avatar klutt‭ · 2020-08-11T08:45:25Z (over 4 years ago)
Is it undefined behaviour to just make a pointer point outside boundaries of an array without dereferencing it?
I have heard that it is undefined behaviour to make a pointer point outside boundaries of an array even without dereferencing it. Can that really be true? Consider this code:

    char arr[10];
    char *ptr = arr[-1];
    char c = *ptr;

The third line is obviously bad, because it's accessing out of bounds. But I heard something that even the second line invokes undefined behaviour? Is this true? What does the standard say?