Download your favorite Linux distribution at LQ ISO.
Go Back > Forums > Linux Forums > Linux - Software
User Name
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.


  Search this Thread
Old 09-16-2014, 07:48 AM   #1
LQ Newbie
Registered: Dec 2011
Posts: 1

Rep: Reputation: Disabled
Smile Stack memory area print that would show symbols and memory address using GDB

I am seeing some stack smashing issue in my program. I have used btrace /where and could see where the problem is. I would like get a complete view of the stack during this issue, to when the stack overflow is happening what all memory areas of my code are getting corrupted How would I do that? The current support with btrace/where just limits to the parameter in scope, but doesn't show the stack overflowen/corrupted area. Please advice.
Let me know if anymore details required.

Old 09-21-2014, 06:11 PM   #2
Registered: Aug 2005
Location: Anchorage, Alaska (soon EU, hopefully)
Distribution: Anything NOT SystemD (ie. M$) related.
Posts: 918

Rep: Reputation: 42
Have you gotten any answers yet.. from anywhere?

I wish I could suggest something more thorough than trace.. but my programming/detective skills are not up to date .. at least not in the details of memory maps.

How about assembler tools? Might be overkill.. but there might be something there..

I would think.. Linux has a multitude of programs and plugins, that would help solve your request..

Last edited by halvy; 09-21-2014 at 06:12 PM.
Old 09-21-2014, 08:40 PM   #3
Registered: Sep 2003
Location: 19th moon ................. ................Planet Covid ................Another Galaxy;............. ................Not Yours
Posts: 705

Rep: Reputation: Disabled
Hi narasimhap,

Are you still looking for answers?

If the details of the situation warrant it, have you considered using watchpoints?

If it's appropriate for your situation, have you tried mtrace? mtrace may make use of malloc_hook's which are technically deprecated, but even if it does, if you still have mtrace on your system, you might want to give it a try.

Have you consulted the info doc on gdb? It contains a wealth of information.



Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] gdb reports "Cannot access memory at address 0x8049088". stf92 Programming 3 07-11-2011 07:11 PM
shared memory address area in process address space nagaraju1024 Programming 3 02-22-2011 05:49 AM
Application Virtual address space memory allocation - memory does not get free chamara82 Linux - General 4 01-01-2011 09:19 PM
Shared Memory - Should they show the same address? threepointonefour Programming 2 03-17-2010 05:07 PM
gdb : Cannot access memory at address 0x99f825d4 johnpaulodonnell Linux - Newbie 1 03-23-2007 09:14 PM > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 11:57 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration