How to debug cannot access address using gdb

Question

When I try to debug core file with gdb I dont see any valid stack trace to proceed further (similar to the reported issue in the link below). Can you please help me how I should debug further to debug the issue. Any pointers or gdb commands which will help in triaging the problem.

GDB debugging trace with no relevant info (#0 0x2e6e6f69 in ?? ())

(gdb) where
#0  0x76c0da28 in ?? ()
#1  0x76c0d9e0 in ?? ()
#2  0x76c0d9e0 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)

EDIT: To rule out the possibility of the -g flag and host environment issues,I have intentionally added a code to crash and was able to get the correct stack trace from the corefile.

The corrupt stack message could indicate that something went wrong with your memory access ( most certainly invalid write ), other tools like valgrind could help figure out your issue. — dvhh
– dvhh, Commented Jan 10, 2017 at 7:50

Community · Accepted Answer · 2017-05-23 12:07:19Z

1

When I try to debug core file with gdb I dont see any valid stack trace

Was the core produced on the same host where it is being analyzed?

If not, this answer explains what you need to do.

edited May 23, 2017 at 12:07

CommunityBot

11 silver badge

answered Jan 10, 2017 at 19:09

Employed Russian

217k36 gold badges324 silver badges396 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

foo_l Over a year ago

Yes it is on same host.

RokeJulianLockhart May 26 at 1:28

Same host here, too. As absurd as it seems, per github.com/Murmele/Gittyup/issues/523#issuecomment-2908255630, the speed with which you type bt full determines whether the RAM addresses remain.

Collectives™ on Stack Overflow

How to debug cannot access address using gdb

1 Answer 1

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related