Find base address and memory size of program debugged in gdb

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I want to find out the base address and the imagesize of the program being debugged in gdb. As in, where it got loaded in memory. For shared libraries I can do "info sharedlibrary" and I get very nice output like so:



0x00007ffff7dd5f10 0x00007ffff7df4b20 Yes /lib64/ld-linux-x86-64.so.2


How can i get this output for the main program i am debugging?



I know that gdb disables ASLR and I could just inspect the ELF file myself to find out, but there has to be a way via gdb too.



(Background: I am using gdb's mi, and I can keep a basic overview of where things are by parsing sharedlibrary-load messages. But it never sends such a message for the main program, which is the most important thing.)



Thanks!






debugging gdb debuggers elf







share|improve this question





















  • pmap -x [pid] ( linux.die.net/man/1/pmap ) from the command line may probably help you without gdb
    – w s
    1 hour ago















up vote
1
down vote

favorite












I want to find out the base address and the imagesize of the program being debugged in gdb. As in, where it got loaded in memory. For shared libraries I can do "info sharedlibrary" and I get very nice output like so:



0x00007ffff7dd5f10 0x00007ffff7df4b20 Yes /lib64/ld-linux-x86-64.so.2


How can i get this output for the main program i am debugging?



I know that gdb disables ASLR and I could just inspect the ELF file myself to find out, but there has to be a way via gdb too.



(Background: I am using gdb's mi, and I can keep a basic overview of where things are by parsing sharedlibrary-load messages. But it never sends such a message for the main program, which is the most important thing.)



Thanks!






debugging gdb debuggers elf







share|improve this question





















  • pmap -x [pid] ( linux.die.net/man/1/pmap ) from the command line may probably help you without gdb
    – w s
    1 hour ago













up vote
1
down vote

favorite









up vote
1
down vote

favorite











I want to find out the base address and the imagesize of the program being debugged in gdb. As in, where it got loaded in memory. For shared libraries I can do "info sharedlibrary" and I get very nice output like so:



0x00007ffff7dd5f10 0x00007ffff7df4b20 Yes /lib64/ld-linux-x86-64.so.2


How can i get this output for the main program i am debugging?



I know that gdb disables ASLR and I could just inspect the ELF file myself to find out, but there has to be a way via gdb too.



(Background: I am using gdb's mi, and I can keep a basic overview of where things are by parsing sharedlibrary-load messages. But it never sends such a message for the main program, which is the most important thing.)



Thanks!






debugging gdb debuggers elf







share|improve this question













I want to find out the base address and the imagesize of the program being debugged in gdb. As in, where it got loaded in memory. For shared libraries I can do "info sharedlibrary" and I get very nice output like so:



0x00007ffff7dd5f10 0x00007ffff7df4b20 Yes /lib64/ld-linux-x86-64.so.2


How can i get this output for the main program i am debugging?



I know that gdb disables ASLR and I could just inspect the ELF file myself to find out, but there has to be a way via gdb too.



(Background: I am using gdb's mi, and I can keep a basic overview of where things are by parsing sharedlibrary-load messages. But it never sends such a message for the main program, which is the most important thing.)



Thanks!






debugging gdb debuggers elf




debugging gdb debuggers elf






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 3 hours ago









bernd feinman

1035




1035











  • pmap -x [pid] ( linux.die.net/man/1/pmap ) from the command line may probably help you without gdb
    – w s
    1 hour ago

















  • pmap -x [pid] ( linux.die.net/man/1/pmap ) from the command line may probably help you without gdb
    – w s
    1 hour ago
















pmap -x [pid] ( linux.die.net/man/1/pmap ) from the command line may probably help you without gdb
– w s
1 hour ago





pmap -x [pid] ( linux.die.net/man/1/pmap ) from the command line may probably help you without gdb
– w s
1 hour ago











2 Answers
2






active

oldest

votes

















up vote
2
down vote













info file shows the memory map of the current process:



Local exec file:
 `/bin/less', file type elf64-x86-64.
 Entry point: 0x402080
 0x0000000000400238 - 0x0000000000400254 is .interp
 0x0000000000400254 - 0x0000000000400274 is .note.ABI-tag
 0x0000000000400274 - 0x0000000000400298 is .note.gnu.build-id
 0x0000000000400298 - 0x00000000004002e0 is .gnu.hash
 0x00000000004002e0 - 0x0000000000400b20 is .dynsym
 0x0000000000400b20 - 0x0000000000400e7d is .dynstr
 0x0000000000400e7e - 0x0000000000400f2e is .gnu.version
 0x0000000000400f30 - 0x0000000000400fa0 is .gnu.version_r
 0x0000000000400fa0 - 0x0000000000401000 is .rela.dyn
 0x0000000000401000 - 0x0000000000401708 is .rela.plt
 0x0000000000401708 - 0x0000000000401722 is .init
 0x0000000000401730 - 0x0000000000401bf0 is .plt
 0x0000000000401bf0 - 0x0000000000415824 is .text
 0x0000000000415824 - 0x000000000041582d is .fini
 0x0000000000415840 - 0x000000000041bd67 is .rodata
 0x000000000041bd68 - 0x000000000041c90c is .eh_frame_hdr
 0x000000000041c910 - 0x00000000004208e4 is .eh_frame
 0x0000000000620e00 - 0x0000000000620e08 is .init_array
 0x0000000000620e08 - 0x0000000000620e10 is .fini_array
 0x0000000000620e10 - 0x0000000000620e18 is .jcr
 0x0000000000620e18 - 0x0000000000620ff8 is .dynamic
 0x0000000000620ff8 - 0x0000000000621000 is .got
 0x0000000000621000 - 0x0000000000621270 is .got.plt
 0x0000000000621280 - 0x000000000062500c is .data
 0x00007fffff4001c8 - 0x00007fffff4001ec is .note.gnu.build-id in /lib64/ld-linux-x86-64.so.2
 0x00007fffff4001f0 - 0x00007fffff4002ac is .hash in /lib64/ld-linux-x86-64.so.2
 0x00007fffff4002b0 - 0x00007fffff40038c is .gnu.hash in /lib64/ld-linux-x86-64.so.2
 0x00007fffff400390 - 0x00007fffff400630 is .dynsym in /lib64/ld-linux-x86-64.so.2


Lines without a filename at the end are those for the main executable.






share|improve this answer



























    up vote
    2
    down vote













    You can do the following:




    • info inferior or print getpid() gives you a process id


    • shell pmap -x the process id gives you a memory map of the process (it is not functionality of gdb, pmap is other shell command, but it is a bit better then analyzing ELF)

    • You can also use shell cat /proc/pid/maps file (as far as I understand pmap just parses and prints its content)

    You'll see something like this(it's a result of a process named opt which I am debugging just now):



    6648: /home/ubuntu/llvm-5.0.1.src/build/bin/opt
    Address Kbytes RSS Dirty Mode Mapping
    0000000000400000 100524 36380 8 r-x-- opt
    0000000000400000 0 0 0 r-x-- opt
    000000000682a000 4176 356 296 r---- opt
    000000000682a000 0 0 0 r---- opt
    0000000006c3e000 628 76 76 rw--- opt
    0000000006c3e000 0 0 0 rw--- opt
    0000000006cdb000 684 480 480 rw--- [ anon ]
    0000000006cdb000 0 0 0 rw--- [ anon ]
    00007ffff6908000 1792 1056 8 r-x-- libc-2.23.so
    00007ffff6908000 0 0 0 r-x-- libc-2.23.so
    00007ffff6ac8000 2048 0 0 ----- libc-2.23.so
    00007ffff6ac8000 0 0 0 ----- libc-2.23.so
    00007ffff6cc8000 16 16 16 r---- libc-2.23.so
    00007ffff6cc8000 0 0 0 r---- libc-2.23.so
    00007ffff6ccc000 8 8 8 rw--- libc-2.23.so
    00007ffff6ccc000 0 0 0 rw--- libc-2.23.so
    00007ffff6cce000 16 12 12 rw--- [ anon ]
    00007ffff6cce000 0 0 0 rw--- [ anon ]
    ...
    ...


    If I understand your question correctly the line



     0000000000400000 100524 36380 8 r-x-- opt


    is what you need.






    share|improve this answer






















      Your Answer







      StackExchange.ready(function()
      var channelOptions =
      tags: "".split(" "),
      id: "489"
      ;
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function()
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled)
      StackExchange.using("snippets", function()
      createEditor();
      );

      else
      createEditor();

      );

      function createEditor()
      StackExchange.prepareEditor(
      heartbeatType: 'answer',
      convertImagesToLinks: false,
      noModals: false,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      noCode: true, onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      );



      );













       

      draft saved


      draft discarded


















      StackExchange.ready(
      function ()
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2freverseengineering.stackexchange.com%2fquestions%2f19598%2ffind-base-address-and-memory-size-of-program-debugged-in-gdb%23new-answer', 'question_page');

      );

      Post as a guest

















      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      2
      down vote













      info file shows the memory map of the current process:



      Local exec file:
       `/bin/less', file type elf64-x86-64.
       Entry point: 0x402080
       0x0000000000400238 - 0x0000000000400254 is .interp
       0x0000000000400254 - 0x0000000000400274 is .note.ABI-tag
       0x0000000000400274 - 0x0000000000400298 is .note.gnu.build-id
       0x0000000000400298 - 0x00000000004002e0 is .gnu.hash
       0x00000000004002e0 - 0x0000000000400b20 is .dynsym
       0x0000000000400b20 - 0x0000000000400e7d is .dynstr
       0x0000000000400e7e - 0x0000000000400f2e is .gnu.version
       0x0000000000400f30 - 0x0000000000400fa0 is .gnu.version_r
       0x0000000000400fa0 - 0x0000000000401000 is .rela.dyn
       0x0000000000401000 - 0x0000000000401708 is .rela.plt
       0x0000000000401708 - 0x0000000000401722 is .init
       0x0000000000401730 - 0x0000000000401bf0 is .plt
       0x0000000000401bf0 - 0x0000000000415824 is .text
       0x0000000000415824 - 0x000000000041582d is .fini
       0x0000000000415840 - 0x000000000041bd67 is .rodata
       0x000000000041bd68 - 0x000000000041c90c is .eh_frame_hdr
       0x000000000041c910 - 0x00000000004208e4 is .eh_frame
       0x0000000000620e00 - 0x0000000000620e08 is .init_array
       0x0000000000620e08 - 0x0000000000620e10 is .fini_array
       0x0000000000620e10 - 0x0000000000620e18 is .jcr
       0x0000000000620e18 - 0x0000000000620ff8 is .dynamic
       0x0000000000620ff8 - 0x0000000000621000 is .got
       0x0000000000621000 - 0x0000000000621270 is .got.plt
       0x0000000000621280 - 0x000000000062500c is .data
       0x00007fffff4001c8 - 0x00007fffff4001ec is .note.gnu.build-id in /lib64/ld-linux-x86-64.so.2
       0x00007fffff4001f0 - 0x00007fffff4002ac is .hash in /lib64/ld-linux-x86-64.so.2
       0x00007fffff4002b0 - 0x00007fffff40038c is .gnu.hash in /lib64/ld-linux-x86-64.so.2
       0x00007fffff400390 - 0x00007fffff400630 is .dynsym in /lib64/ld-linux-x86-64.so.2


      Lines without a filename at the end are those for the main executable.






      share|improve this answer
























        up vote
        2
        down vote













        info file shows the memory map of the current process:



        Local exec file:
         `/bin/less', file type elf64-x86-64.
         Entry point: 0x402080
         0x0000000000400238 - 0x0000000000400254 is .interp
         0x0000000000400254 - 0x0000000000400274 is .note.ABI-tag
         0x0000000000400274 - 0x0000000000400298 is .note.gnu.build-id
         0x0000000000400298 - 0x00000000004002e0 is .gnu.hash
         0x00000000004002e0 - 0x0000000000400b20 is .dynsym
         0x0000000000400b20 - 0x0000000000400e7d is .dynstr
         0x0000000000400e7e - 0x0000000000400f2e is .gnu.version
         0x0000000000400f30 - 0x0000000000400fa0 is .gnu.version_r
         0x0000000000400fa0 - 0x0000000000401000 is .rela.dyn
         0x0000000000401000 - 0x0000000000401708 is .rela.plt
         0x0000000000401708 - 0x0000000000401722 is .init
         0x0000000000401730 - 0x0000000000401bf0 is .plt
         0x0000000000401bf0 - 0x0000000000415824 is .text
         0x0000000000415824 - 0x000000000041582d is .fini
         0x0000000000415840 - 0x000000000041bd67 is .rodata
         0x000000000041bd68 - 0x000000000041c90c is .eh_frame_hdr
         0x000000000041c910 - 0x00000000004208e4 is .eh_frame
         0x0000000000620e00 - 0x0000000000620e08 is .init_array
         0x0000000000620e08 - 0x0000000000620e10 is .fini_array
         0x0000000000620e10 - 0x0000000000620e18 is .jcr
         0x0000000000620e18 - 0x0000000000620ff8 is .dynamic
         0x0000000000620ff8 - 0x0000000000621000 is .got
         0x0000000000621000 - 0x0000000000621270 is .got.plt
         0x0000000000621280 - 0x000000000062500c is .data
         0x00007fffff4001c8 - 0x00007fffff4001ec is .note.gnu.build-id in /lib64/ld-linux-x86-64.so.2
         0x00007fffff4001f0 - 0x00007fffff4002ac is .hash in /lib64/ld-linux-x86-64.so.2
         0x00007fffff4002b0 - 0x00007fffff40038c is .gnu.hash in /lib64/ld-linux-x86-64.so.2
         0x00007fffff400390 - 0x00007fffff400630 is .dynsym in /lib64/ld-linux-x86-64.so.2


        Lines without a filename at the end are those for the main executable.






        share|improve this answer






















          up vote
          2
          down vote










          up vote
          2
          down vote









          info file shows the memory map of the current process:



          Local exec file:
           `/bin/less', file type elf64-x86-64.
           Entry point: 0x402080
           0x0000000000400238 - 0x0000000000400254 is .interp
           0x0000000000400254 - 0x0000000000400274 is .note.ABI-tag
           0x0000000000400274 - 0x0000000000400298 is .note.gnu.build-id
           0x0000000000400298 - 0x00000000004002e0 is .gnu.hash
           0x00000000004002e0 - 0x0000000000400b20 is .dynsym
           0x0000000000400b20 - 0x0000000000400e7d is .dynstr
           0x0000000000400e7e - 0x0000000000400f2e is .gnu.version
           0x0000000000400f30 - 0x0000000000400fa0 is .gnu.version_r
           0x0000000000400fa0 - 0x0000000000401000 is .rela.dyn
           0x0000000000401000 - 0x0000000000401708 is .rela.plt
           0x0000000000401708 - 0x0000000000401722 is .init
           0x0000000000401730 - 0x0000000000401bf0 is .plt
           0x0000000000401bf0 - 0x0000000000415824 is .text
           0x0000000000415824 - 0x000000000041582d is .fini
           0x0000000000415840 - 0x000000000041bd67 is .rodata
           0x000000000041bd68 - 0x000000000041c90c is .eh_frame_hdr
           0x000000000041c910 - 0x00000000004208e4 is .eh_frame
           0x0000000000620e00 - 0x0000000000620e08 is .init_array
           0x0000000000620e08 - 0x0000000000620e10 is .fini_array
           0x0000000000620e10 - 0x0000000000620e18 is .jcr
           0x0000000000620e18 - 0x0000000000620ff8 is .dynamic
           0x0000000000620ff8 - 0x0000000000621000 is .got
           0x0000000000621000 - 0x0000000000621270 is .got.plt
           0x0000000000621280 - 0x000000000062500c is .data
           0x00007fffff4001c8 - 0x00007fffff4001ec is .note.gnu.build-id in /lib64/ld-linux-x86-64.so.2
           0x00007fffff4001f0 - 0x00007fffff4002ac is .hash in /lib64/ld-linux-x86-64.so.2
           0x00007fffff4002b0 - 0x00007fffff40038c is .gnu.hash in /lib64/ld-linux-x86-64.so.2
           0x00007fffff400390 - 0x00007fffff400630 is .dynsym in /lib64/ld-linux-x86-64.so.2


          Lines without a filename at the end are those for the main executable.






          share|improve this answer












          info file shows the memory map of the current process:



          Local exec file:
           `/bin/less', file type elf64-x86-64.
           Entry point: 0x402080
           0x0000000000400238 - 0x0000000000400254 is .interp
           0x0000000000400254 - 0x0000000000400274 is .note.ABI-tag
           0x0000000000400274 - 0x0000000000400298 is .note.gnu.build-id
           0x0000000000400298 - 0x00000000004002e0 is .gnu.hash
           0x00000000004002e0 - 0x0000000000400b20 is .dynsym
           0x0000000000400b20 - 0x0000000000400e7d is .dynstr
           0x0000000000400e7e - 0x0000000000400f2e is .gnu.version
           0x0000000000400f30 - 0x0000000000400fa0 is .gnu.version_r
           0x0000000000400fa0 - 0x0000000000401000 is .rela.dyn
           0x0000000000401000 - 0x0000000000401708 is .rela.plt
           0x0000000000401708 - 0x0000000000401722 is .init
           0x0000000000401730 - 0x0000000000401bf0 is .plt
           0x0000000000401bf0 - 0x0000000000415824 is .text
           0x0000000000415824 - 0x000000000041582d is .fini
           0x0000000000415840 - 0x000000000041bd67 is .rodata
           0x000000000041bd68 - 0x000000000041c90c is .eh_frame_hdr
           0x000000000041c910 - 0x00000000004208e4 is .eh_frame
           0x0000000000620e00 - 0x0000000000620e08 is .init_array
           0x0000000000620e08 - 0x0000000000620e10 is .fini_array
           0x0000000000620e10 - 0x0000000000620e18 is .jcr
           0x0000000000620e18 - 0x0000000000620ff8 is .dynamic
           0x0000000000620ff8 - 0x0000000000621000 is .got
           0x0000000000621000 - 0x0000000000621270 is .got.plt
           0x0000000000621280 - 0x000000000062500c is .data
           0x00007fffff4001c8 - 0x00007fffff4001ec is .note.gnu.build-id in /lib64/ld-linux-x86-64.so.2
           0x00007fffff4001f0 - 0x00007fffff4002ac is .hash in /lib64/ld-linux-x86-64.so.2
           0x00007fffff4002b0 - 0x00007fffff40038c is .gnu.hash in /lib64/ld-linux-x86-64.so.2
           0x00007fffff400390 - 0x00007fffff400630 is .dynsym in /lib64/ld-linux-x86-64.so.2


          Lines without a filename at the end are those for the main executable.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 21 mins ago









          Igor Skochinsky♦

          23.1k34185




          23.1k34185




















              up vote
              2
              down vote













              You can do the following:




              • info inferior or print getpid() gives you a process id


              • shell pmap -x the process id gives you a memory map of the process (it is not functionality of gdb, pmap is other shell command, but it is a bit better then analyzing ELF)

              • You can also use shell cat /proc/pid/maps file (as far as I understand pmap just parses and prints its content)

              You'll see something like this(it's a result of a process named opt which I am debugging just now):



              6648: /home/ubuntu/llvm-5.0.1.src/build/bin/opt
              Address Kbytes RSS Dirty Mode Mapping
              0000000000400000 100524 36380 8 r-x-- opt
              0000000000400000 0 0 0 r-x-- opt
              000000000682a000 4176 356 296 r---- opt
              000000000682a000 0 0 0 r---- opt
              0000000006c3e000 628 76 76 rw--- opt
              0000000006c3e000 0 0 0 rw--- opt
              0000000006cdb000 684 480 480 rw--- [ anon ]
              0000000006cdb000 0 0 0 rw--- [ anon ]
              00007ffff6908000 1792 1056 8 r-x-- libc-2.23.so
              00007ffff6908000 0 0 0 r-x-- libc-2.23.so
              00007ffff6ac8000 2048 0 0 ----- libc-2.23.so
              00007ffff6ac8000 0 0 0 ----- libc-2.23.so
              00007ffff6cc8000 16 16 16 r---- libc-2.23.so
              00007ffff6cc8000 0 0 0 r---- libc-2.23.so
              00007ffff6ccc000 8 8 8 rw--- libc-2.23.so
              00007ffff6ccc000 0 0 0 rw--- libc-2.23.so
              00007ffff6cce000 16 12 12 rw--- [ anon ]
              00007ffff6cce000 0 0 0 rw--- [ anon ]
              ...
              ...


              If I understand your question correctly the line



               0000000000400000 100524 36380 8 r-x-- opt


              is what you need.






              share|improve this answer


























                up vote
                2
                down vote













                You can do the following:




                • info inferior or print getpid() gives you a process id


                • shell pmap -x the process id gives you a memory map of the process (it is not functionality of gdb, pmap is other shell command, but it is a bit better then analyzing ELF)

                • You can also use shell cat /proc/pid/maps file (as far as I understand pmap just parses and prints its content)

                You'll see something like this(it's a result of a process named opt which I am debugging just now):



                6648: /home/ubuntu/llvm-5.0.1.src/build/bin/opt
                Address Kbytes RSS Dirty Mode Mapping
                0000000000400000 100524 36380 8 r-x-- opt
                0000000000400000 0 0 0 r-x-- opt
                000000000682a000 4176 356 296 r---- opt
                000000000682a000 0 0 0 r---- opt
                0000000006c3e000 628 76 76 rw--- opt
                0000000006c3e000 0 0 0 rw--- opt
                0000000006cdb000 684 480 480 rw--- [ anon ]
                0000000006cdb000 0 0 0 rw--- [ anon ]
                00007ffff6908000 1792 1056 8 r-x-- libc-2.23.so
                00007ffff6908000 0 0 0 r-x-- libc-2.23.so
                00007ffff6ac8000 2048 0 0 ----- libc-2.23.so
                00007ffff6ac8000 0 0 0 ----- libc-2.23.so
                00007ffff6cc8000 16 16 16 r---- libc-2.23.so
                00007ffff6cc8000 0 0 0 r---- libc-2.23.so
                00007ffff6ccc000 8 8 8 rw--- libc-2.23.so
                00007ffff6ccc000 0 0 0 rw--- libc-2.23.so
                00007ffff6cce000 16 12 12 rw--- [ anon ]
                00007ffff6cce000 0 0 0 rw--- [ anon ]
                ...
                ...


                If I understand your question correctly the line



                 0000000000400000 100524 36380 8 r-x-- opt


                is what you need.






                share|improve this answer
























                  up vote
                  2
                  down vote










                  up vote
                  2
                  down vote









                  You can do the following:




                  • info inferior or print getpid() gives you a process id


                  • shell pmap -x the process id gives you a memory map of the process (it is not functionality of gdb, pmap is other shell command, but it is a bit better then analyzing ELF)

                  • You can also use shell cat /proc/pid/maps file (as far as I understand pmap just parses and prints its content)

                  You'll see something like this(it's a result of a process named opt which I am debugging just now):



                  6648: /home/ubuntu/llvm-5.0.1.src/build/bin/opt
                  Address Kbytes RSS Dirty Mode Mapping
                  0000000000400000 100524 36380 8 r-x-- opt
                  0000000000400000 0 0 0 r-x-- opt
                  000000000682a000 4176 356 296 r---- opt
                  000000000682a000 0 0 0 r---- opt
                  0000000006c3e000 628 76 76 rw--- opt
                  0000000006c3e000 0 0 0 rw--- opt
                  0000000006cdb000 684 480 480 rw--- [ anon ]
                  0000000006cdb000 0 0 0 rw--- [ anon ]
                  00007ffff6908000 1792 1056 8 r-x-- libc-2.23.so
                  00007ffff6908000 0 0 0 r-x-- libc-2.23.so
                  00007ffff6ac8000 2048 0 0 ----- libc-2.23.so
                  00007ffff6ac8000 0 0 0 ----- libc-2.23.so
                  00007ffff6cc8000 16 16 16 r---- libc-2.23.so
                  00007ffff6cc8000 0 0 0 r---- libc-2.23.so
                  00007ffff6ccc000 8 8 8 rw--- libc-2.23.so
                  00007ffff6ccc000 0 0 0 rw--- libc-2.23.so
                  00007ffff6cce000 16 12 12 rw--- [ anon ]
                  00007ffff6cce000 0 0 0 rw--- [ anon ]
                  ...
                  ...


                  If I understand your question correctly the line



                   0000000000400000 100524 36380 8 r-x-- opt


                  is what you need.






                  share|improve this answer














                  You can do the following:




                  • info inferior or print getpid() gives you a process id


                  • shell pmap -x the process id gives you a memory map of the process (it is not functionality of gdb, pmap is other shell command, but it is a bit better then analyzing ELF)

                  • You can also use shell cat /proc/pid/maps file (as far as I understand pmap just parses and prints its content)

                  You'll see something like this(it's a result of a process named opt which I am debugging just now):



                  6648: /home/ubuntu/llvm-5.0.1.src/build/bin/opt
                  Address Kbytes RSS Dirty Mode Mapping
                  0000000000400000 100524 36380 8 r-x-- opt
                  0000000000400000 0 0 0 r-x-- opt
                  000000000682a000 4176 356 296 r---- opt
                  000000000682a000 0 0 0 r---- opt
                  0000000006c3e000 628 76 76 rw--- opt
                  0000000006c3e000 0 0 0 rw--- opt
                  0000000006cdb000 684 480 480 rw--- [ anon ]
                  0000000006cdb000 0 0 0 rw--- [ anon ]
                  00007ffff6908000 1792 1056 8 r-x-- libc-2.23.so
                  00007ffff6908000 0 0 0 r-x-- libc-2.23.so
                  00007ffff6ac8000 2048 0 0 ----- libc-2.23.so
                  00007ffff6ac8000 0 0 0 ----- libc-2.23.so
                  00007ffff6cc8000 16 16 16 r---- libc-2.23.so
                  00007ffff6cc8000 0 0 0 r---- libc-2.23.so
                  00007ffff6ccc000 8 8 8 rw--- libc-2.23.so
                  00007ffff6ccc000 0 0 0 rw--- libc-2.23.so
                  00007ffff6cce000 16 12 12 rw--- [ anon ]
                  00007ffff6cce000 0 0 0 rw--- [ anon ]
                  ...
                  ...


                  If I understand your question correctly the line



                   0000000000400000 100524 36380 8 r-x-- opt


                  is what you need.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited 18 mins ago

























                  answered 1 hour ago









                  w s

                  6,73811332




                  6,73811332



























                       

                      draft saved


                      draft discarded















































                       


                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2freverseengineering.stackexchange.com%2fquestions%2f19598%2ffind-base-address-and-memory-size-of-program-debugged-in-gdb%23new-answer', 'question_page');

                      );

                      Post as a guest
































































                      Comments

                      Post a Comment

                      Popular posts from this blog

                      What does second last employer means? [closed]

                      Image
                      Clash Royale CLAN TAG #URR8PPP .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0; up vote -3 down vote favorite Say, for example I have worked in the following companies, Company A => 2010 - 2011 Company B => 2011 - 2012 Company C => 2012 - Till Date Company D => Have offer Now assume Company D is asking to submit documents from my second last employer. So from the list of companies given, which company would be qualified as second last employer? software-industry employer share | improve this question asked Aug 10 '14 at 5:16 Rajaprabhu Aravindasamy 559 1 6 13 closed as off-topic by Jim G., jmort253 ♦ Aug 11 '14 at 1:58 This question appears to be off-topic. The users who voted to close gave this specific reason: "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address...
                      Read more

                      List of Gilmore Girls characters

                      Image
                      The season three cast—(Back row): Lane, Michel, Paris, Emily, Richard, Sookie, Miss Patty, Kirk; Front row: Jess, Luke, Lorelai, Rory, Dean This is a list of characters for the comedy-drama television series Gilmore Girls . Contents 1 Main characters 1.1 Lorelai Gilmore 1.2 Rory Gilmore 1.3 Sookie St. James 1.4 Lane Kim 1.5 Michel Gerard 1.6 Luke Danes 1.7 Emily Gilmore 1.8 Richard Gilmore 1.9 Paris Geller 1.10 Dean Forester 1.11 Jess Mariano 1.12 Kirk Gleason 1.13 Jason Stiles 1.14 Logan Huntzberger 2 Major recurring characters 2.1 Christopher Hayden 2.2 Jackson Belleville 2.3 Mrs. Kim 2.4 Tristin DuGray 2.5 Max Medina 2.6 Taylor Doose 2.7 Dave Rygalski 2.8 Marty 3 Recurring characters 3.1 Stars Hollow 3.2 Chilton 3.3 Yale 3.4 Other 4 Notable guest stars 5 Unseen characters 6 Notes 7 References Main characters Actor Character Appearances Season 1 Season 2 Season 3 Season 4 Season 5 Season 6 Season 7 A Year in the Life Lauren Graham Lorelai Gilmore...
                      Read more

                      Confectionery

                      Image
                      Prepared foods made with a lot of sugar or other cabohydrates "Sweetmeat" redirects here. For the racehorse, see Sweetmeat (horse). Not to be confused with Sweetbread. This Kransekake is a traditional Scandinavian baker's confection. Confectionery is the art of making confections , which are food items that are rich in sugar and carbohydrates. Exact definitions are difficult. [1] In general, though, confectionery is divided into two broad and somewhat overlapping categories, bakers' confections and sugar confections. [2] Bakers' confectionery, also called flour confections , includes principally sweet pastries, cakes, and similar baked goods. Sugar confectionery includes candies ( sweets in British English), candied nuts, chocolates, chewing gum, bubble gum, pastillage, and other confections that are made primarily of sugar. In some cases, chocolate confections (confections made of chocolate) are treated as a separate category, as are sugar-free versions of ...
                      Read more