From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Wiles, Keith" Subject: Re: Debug info Date: Mon, 20 Apr 2015 18:04:16 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable To: Shankari Vaidyalingam , "dev-VfR2kkLFssw@public.gmane.org" Return-path: In-Reply-To: Content-Language: en-US Content-ID: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On 4/20/15, 12:51 PM, "Shankari Vaidyalingam" wrote: >Hi, > >I have developed an application with DPDK. >While executing the same I can see the application quitting half way (i.e >producing only half of the expected output - terminating abruptly). >I think that something is going wrong which is causing the program to >crash. > >Would like to know if it is possible to get the crashdump with programs >written in DPDK. >If possible please let me know how I can use GDB to debug the crash. >I have heard that rte_panic is used for creating stack trace. As per my >understanding I think that can be done if I know the exact statement which >is causing the crash. But in my application I'm not able to trace the >exact >location of failure as the output differs during each run. I use gdb and cgdb to debug pktgen application on Ubuntu 14.04 sudo cgdb ./app/pktgen Then gdb> run -c 1f -n 2 =8A This works very well, but you need to make sure you compile DPDK and your application with option -g or -g -O0 Using =8Cmake install T=3Dx86_64-native-linuxapp-xclang=B9 EXTRA_CFLAGS+=3D= =B3-g -O0"'=20 > >Pls help. > >Regards >Shankari.V