Summary: | Segmentation fault when executing: python gdb.execute("interp mi '-break-list'") | ||
---|---|---|---|
Product: | gdb | Reporter: | ovparvu |
Component: | python | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | krinkodot22, ssbssa, tromey |
Priority: | P2 | ||
Version: | HEAD | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Last reconfirmed: | 2018-08-17 00:00:00 |
Description
ovparvu
2018-08-17 11:02:55 UTC
Thanks. It's easy to fix this, but I'm finding it challenging to write a test case, because two gdb prompts are printed and gdb_test doesn't like that: (gdb) python gdb.execute("interp mi -break-list") ^done,BreakpointTable={nr_rows="0",nr_cols="6",hdr=[{width="7",alignment="-1",col_name="number",colhdr="Num"},{width="14",alignment="-1",col_name="type",colhdr="Type"},{width="4",alignment="-1",col_name="disp",colhdr="Disp"},{width="3",alignment="-1",col_name="enabled",colhdr="Enb"},{width="10",alignment="-1",col_name="addr",colhdr="Address"},{width="40",alignment="2",col_name="what",colhdr="What"}],body=[]} (gdb) (gdb) ^^^^^^^^^^^ this is bad I am not sure what's going on there yet. The prompt seems to indicate some deeper problem, because with my patch to avoid the crash, after the command gdb gets a bit wedged -- I can't type to it. See bug #21388 This appears to have been introduced in gdb 8.2. Previous gdb versions (I've tested 7.12.1, 8.0.1, and 8.1.1) hit the bad CLI behaviour of bug #21388, but not a segfault. And it's not just 'interp mi -break-list' that triggers the segfault/CLI badness, but any interp/interpreter-exec command. Looks like it's fixed since at least gdb 10.1, maybe someone else knows the details? Seems to be fixed. |