This is the mail archive of the gdb-patches@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] |
>>> On 10.09.18 at 15:01, <simon.marchi@polymtl.ca> wrote: > On 2018-09-10 07:25, Jan Beulich wrote: >>>>> Simon Marchi <simon.marchi@ericsson.com> 09/08/18 1:13 AM >>> >>> Would it be possible to update or create a test to exercise that? >>> arch-specific tests are in testsuite/gdb.arch. >> >> I'm sure it would be possible, but while I was happy to invest the time >> to >> fix the actual bug (because it affects work I'm doing), I'm afraid I >> don't have >> the time to learn how gdb test cases are to be constructed (I'm >> familiar >> only with the binutils / gas side of things). > > I understand. If you can provide: > > - a minimal source file (C + assembly in this case, I suppose) > - GDB commands to reproduce the bug > - actual and expected output Attached. vzero.s is the source file used (no C file needed). gdb.log is a transcript of a session with a broken gdb (the one installed on the system), while gdb.txt is a transcript for the fixed one that I've built myself. > I can take care of turning it in a GDB test case. Thanks. Jan
Attachment:
vzero.s
Description: Binary data
Attachment:
gdb.log
Description: Binary data
Attachment:
gdb.txt
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |