This is the mail archive of the gdb-prs@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]

[Bug gdb/17123] New: x86_x64 gdb "dump binary memory" does not want to use script-based name for dump-file


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

            Bug ID: 17123
           Summary: x86_x64 gdb "dump binary memory" does not want to use
                    script-based name for dump-file
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: critical
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: shprot at mail dot ua

I am write script for gdb for dumping needed regions of memory, and initialize
the string variable for file name. Example script, that I launch when breaking
on some breakpoint with "source" command:

#[SCRIPT BEGIN]

set $mycounter=1
set $rigeonfilename=(void*)malloc(256)
call memset($rigeonfilename,0,256)
call sprintf($rigeonfilename,  "dumpfile%d.mem", $mycounter)
printf "%s\n", $rigeonfilename
dump binary memory $rigeonfilename $rsi $rsi+0x200

#[SCRIPT END]

all executes fine, printf show's normal string that must be there
"dumpfile1.mem", but line dump binary memory creates file on hard drive with
name "$rigeonfilename", but it must be an "dumpfile1.mem", same as that
variable.

In gdb version for x86 was all fine! but x86_x64 it is fails.
Target OS: SUSE 12.2 x86_x64(sure that it will same on all versions, include
last), and gdb I was trying all versions include last. All have same bug.

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


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