This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Debugging issue with -m32 program

From: "Mahmood Naderan via gdb" <gdb at sourceware dot org>
To: "gdb at sourceware dot org" <gdb at sourceware dot org>, Paul Koning <paulkoning at comcast dot net>
Date: Mon, 9 Jul 2018 19:42:56 +0000 (UTC)
Subject: Re: Debugging issue with -m32 program
References: <1810093935.481654.1530980099373.ref@mail.yahoo.com> <1810093935.481654.1530980099373@mail.yahoo.com> <1899779916.938872.1531120747010@mail.yahoo.com> <2E370BA9-E695-4557-AE57-20E68561ACCE@comcast.net>
Reply-to: Mahmood Naderan <nt_mahmood at yahoo dot com>
Reply-to: Mahmood Naderan <nt_mahmood at yahoo dot com>

>Did you overwrite memory by strcpy to an output that's too small?

Indeed yes. But not too small. The buffer is more than 100 characters while dest is 100 characters. The question is why the same program, without specifying -m32, works actually?!
Which one is correct behavior? Crash or not crash?!


Regards,
Mahmood

References:
- Debugging issue with -m32 program
  - From: Mahmood Naderan via gdb
- Re: Debugging issue with -m32 program
  - From: Mahmood Naderan via gdb
- Re: Debugging issue with -m32 program
  - From: Paul Koning

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]