From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 48E203858410; Fri, 17 Mar 2023 11:16:59 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 48E203858410
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1679051819;
	bh=oQ1nCiuyg2K7R/ai9aJ1HKOhIZeZ68KzV4MPBSe0FEY=;
	h=From:To:Subject:Date:From;
	b=LD7pPvtvvJknvb1x0glGEXoweaNV8OqNLrtGXOek/PcYtcgzqtE03REjMpwyChzza
	 OxnJCIaXtP6bAOTikjKRFyJyiSf4lTIvYor5DZJ8V09XzCq0gHp4TJFsUsmRucEuCu
	 4POgCz0vHagCZRfQ+MD686pdZWakZsqn81woNF/s=
From: "czgf2v at 163 dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug macros/30239] New: gdb can't print '__INT_MAX__' in
 '<limits.h>' when debugging c program,but lldb can
Date: Fri, 17 Mar 2023 11:16:58 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: macros
X-Bugzilla-Version: 12.1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: czgf2v at 163 dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: security?
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter target_milestone
 flagtypes.name
Message-ID: <bug-30239-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D30239

            Bug ID: 30239
           Summary: gdb can't print '__INT_MAX__' in '<limits.h>' when
                    debugging c program,but lldb can
           Product: gdb
           Version: 12.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: macros
          Assignee: unassigned at sourceware dot org
          Reporter: czgf2v at 163 dot com
  Target Milestone: ---
             Flags: security?

my current software version
```bash
$ cpp --version
cpp (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
$ gcc --version
gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
```
recently, I upgrade ubuntu from 20 to 22, then the possible bug occurs.
basic.c
```cpp
#include <stddef.h>
#include <stdlib.h>
#include <stdio.h>
#include <assert.h>
#include <limits.h>

int main(int argc, char* argv[]){
    int* basic =3D malloc(sizeof(int));
    *basic =3D INT_MIN;
    *basic =3D INT_MAX;
    *basic+=3D1;
    free(basic);
    return 0;
}
```
I compiled by `gcc -gdwarf-5 -g3 -ggdb3 basic.c -o basic` similar to this
[issue](https://sourceware.org/bugzilla/show_bug.cgi?id=3D29725)
but run gdb `gdb ./basic -ex 'br 11' -ex 'r' -ex 'p __INT_MAX__' -ex 'p
INT_MAX'`
output=20
```
No symbol "__INT_MAX__" in current context.
No symbol "INT_MAX" in current context.
```
in ubuntu 20 I can get "__INT_MAX__" printed but I forgot my env info like
software version in ubuntu 20.
but in `lldb ./basic -o 'breakpoint set -l 11' -o 'r' -o 'p INT_MIN'` with
`(int) $0 =3D -2147483648` output
with `cpp` `INT_MAX` is truly defined
```bash
$ cpp -dM basic.c | grep INT_MAX
#define __WINT_MAX__ 0xffffffffU
#define INT_MAX __INT_MAX__
#define INT_MIN (-INT_MAX - 1)
#define __INT_MAX__ 0x7fffffff
#define UINT_MAX (INT_MAX * 2U + 1U)
```

--=20
You are receiving this mail because:
You are on the CC list for the bug.=