Re: [cdt-dev] strange issue with GDB MI interface with pretty prints

["Ayupov, Andrey" <andrey.ayupov@xxxxxxxxx>]

I was able to create a small/synthetic example that shows the issue. It is attached.
It contains:
compile  - two commands to build main.cpp
gdb_bug_test  - executable if you happen to be able to run (built on suse11 64 bit), otherwise build using compile
gdb_bug_test_pretty_print.cmd  - pretty print script
main.cpp   - source
mi.cmd - MI commands that would make it crash. They use relative paths so it should just run out of the box. 
Can you please see if you can reproduce it? I am planning to file a ticket on gdb next.

Some thoughts. I think the fact that the class for which I create a pretty print actually calls a method to the base class makes a difference. If I create a pretty print for the base class then it seems to work. Maybe I can change my pretty print to do that for now, although it will require user to do an extra click and see extra unnecessary fields from the derived class.

Thanks,
Andrey

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Simon Marchi
Sent: Friday, September 26, 2014 10:07 AM
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] strange issue with GDB MI interface with pretty prints

On 2014-09-26 12:58 PM, Ayupov, Andrey wrote:
> Sorry for the spam, but I jumped to conclusions too soon. Although, I 
> don't see the issue in that set of commands I sent before, it still 
> crashes with similar diagnostics under slightly different conditions. 
> I will debug more and let you know. :(

Ah, bummers :(

Well the process is still the same. Try to reproduce with gdb -i mi and trim the commands until you get the minimal set of commands that reproduce the crash. Like I said though, without the corresponding code, it's a bit difficult for gdb devs to investigate.

Thanks for reporting,

Simon
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cdt-dev
BLOCKED FILE ALERTA file has been blocked due to the 'Intel Email File Filtering Policy' rule.Context: 'gdb_bug_test_pretty_print.cmd'Disallowed due to Ticket Number: '0aac-5425-c73c-000d'

----------------------------------------

BLOCKED FILE ALERTA file has been blocked due to the 'Intel Email File Filtering Policy' rule.Context: 'mi.cmd'Disallowed due to Ticket Number: '0aac-5425-c73c-000d'
See your system administrator for further information. Copyright 1999-2011 McAfee, Inc.All Rights Reserved.http://www.mcafee.com