public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug breakpoints/13346] Multiple breakpoints/losing symbol table issue Date: Wed, 26 Oct 2011 15:13:00 -0000 [thread overview] Message-ID: <bug-13346-4717-GzTlzWlKGb@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13346-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13346 --- Comment #5 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2011-10-26 15:12:28 UTC --- (In reply to comment #4) > Should I be looking at section information for .text? Yes. > libblah.so: > [12] .text PROGBITS 0000000000000540 00000540 > 0000000000000138 0000000000000000 AX 0 0 16 Therefore add for any address you find in /proc/PID/maps 0x540 in this case. > guest# cat /sys/module/openvswitch_mod/sections/.text > 0xffffffffa00ca000 Not sure why they call it `.text' but there is only a probability of 1:4095 that this is really a .text address. Most probably you need to add the .text section address above (from readelf -WS ./openvswitch_mod.ko | grep '\.text'). > (gdb) add-symbol-file ~/vm/openvswitch_mod.ko 0xffffffffa00ca000 > add symbol table from file "/home/jvimal/vm/openvswitch_mod.ko" at > .text_addr = 0xffffffffa00ca000 With probability 99.98% this is wrong address so the GDB behavior is bogus afterwards. > So, both gdb and guest say that the function dp_process_received_packet is at > 0xffffffffa00cd3c8. I do not understand this part but anyway some of the addresses you specified wrongly. Not going to spend debugging a situation which is already wrong. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2011-10-26 15:13 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-25 21:55 [Bug breakpoints/13346] New: " j.vimal at gmail dot com 2011-10-26 7:41 ` [Bug breakpoints/13346] " jan.kratochvil at redhat dot com 2011-10-26 14:36 ` j.vimal at gmail dot com 2011-10-26 14:49 ` jan.kratochvil at redhat dot com 2011-10-26 15:06 ` j.vimal at gmail dot com 2011-10-26 15:13 ` jan.kratochvil at redhat dot com [this message] 2011-10-26 15:51 ` j.vimal at gmail dot com 2011-10-26 16:30 ` jan.kratochvil at redhat dot com 2011-10-27 7:14 ` jan.kiszka at siemens dot com 2011-11-02 13:39 ` tromey at redhat dot com 2011-11-08 0:35 ` jan.kratochvil at redhat dot com 2011-12-02 1:29 ` cvs-commit at gcc dot gnu.org 2011-12-02 1:34 ` jan.kratochvil at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-13346-4717-GzTlzWlKGb@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).