Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] reading non-formatted gdb output

You can use the out-of-band output to figure this out.
We had to do this for catchpoints.  You can look at
CLICatchInfo.parse() for an example.

I hope this helps.


From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Alena Laskavaia [elaskavaia.cdt@xxxxxxxxx]
Sent: August 11, 2015 10:10 AM
To: CDT General developers list.
Subject: [cdt-dev] reading non-formatted gdb output

Hi, I am trying to implement a feature that for postmortem debug so Debug view should show
a signal that killed the program. Gdb prints this when core is loaded as "free text" somewhere
between command to load core and mi reply for this command.
What would be recommended way to hook into the output stream and extract this?

350,742 18-target-select core /home/elaskavaia/Develop/runtime-wipe/linux_c/core
350,743 =thread-group-started,id="i1",pid="27510"
350,744 19-list-thread-groups --available
350,745 =thread-created,id="1",group-id="i1"
350,745 ~"[New LWP 27510]\n"
350,745 =library-loaded,id="/lib/x86_64-linux-gnu/",target-name="/lib/x86_64-linux-gnu/libc\
350,745 =library-loaded,id="/lib64/",target-name="/lib64/",h\
350,751 20-list-thread-groups
350,952 ~"Core was generated by `/home/elaskavaia/Develop/runtime-wipe/linux_c/Debug/linux_c'.\n"
350,953 ~"Program terminated with signal SIGSEGV, Segmentation fault.\n"

350,953 18^connected,frame={level="0",addr="0x0000000000400554",func="main",args=[],file="../src/lin\
350,953 (gdb)

Back to the top