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] |
i'm wondering if it's expected behavior that "run" with the sim target isnt terribly useful for multiple execution. for example, the simple program: main(int argc, char *argv[]) { puts(argv[0]); } loaded up as so: $ gdb ./a.out (gdb) target sim (gdb) load (gdb) run <works fine> (gdb) run <does not work fine> this can be attributed to the "load" loading up the ELF contents into the relevant memory regions, but "run" only executes it. so if the program modifies memory (such as .data), things dont get reloaded and behavior is not so nice. based on the code, i guess this is expected behavior. the trouble comes in with the gdb testsuites that explicitly try and verify that this works. such as gdb.base/a2-run.exp. -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |