Re: Problem with debugging -m32 program

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Gcc-help <gcc-help@xxxxxxxxxxx>, Andrew Haley <aph@xxxxxxxxxx>
Subject: Re: Problem with debugging -m32 program
From: "Mahmood Naderan via gcc-help" <gcc-help@xxxxxxxxxxx>
Date: Mon, 9 Jul 2018 09:10:25 +0000 (UTC)
In-reply-to: <4ed6a067-0fdc-70e5-6169-78ceab50d87f@redhat.com>
References: <1389692863.940105.1531121516930.ref@mail.yahoo.com> <1389692863.940105.1531121516930@mail.yahoo.com> <41fb0a92-3cb4-b68d-52b3-dee88fa4c254@redhat.com> <1735155695.954204.1531123835150@mail.yahoo.com> <4ed6a067-0fdc-70e5-6169-78ceab50d87f@redhat.com>
Reply-to: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
Reply-to: Mahmood Naderan <nt_mahmood@xxxxxxxxx>

>So, your question is not "Why does this crash" but "Why does the -m64
>version not crash?"


Should it crash really? If yes, then I agree with you. Why not specifying m32 doesn't crash?
BTW, I don't explicitly specify -m64. I just use w/o -m32.

Regards,
Mahmood

Follow-Ups:
- Re: Problem with debugging -m32 program
  - From: Andrew Haley

References:
- Problem with debugging -m32 program
  - From: Mahmood Naderan via gcc-help
- Re: Problem with debugging -m32 program
  - From: Andrew Haley
- Re: Problem with debugging -m32 program
  - From: Mahmood Naderan via gcc-help
- Re: Problem with debugging -m32 program
  - From: Andrew Haley

Prev by Date: Re: Problem with debugging -m32 program
Next by Date: Re: invalid 'asm': invalid operand for code 'H'
Previous by thread: Re: Problem with debugging -m32 program
Next by thread: Re: Problem with debugging -m32 program
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux