Bug 479781
| Summary: | gdb trips on "finish" command | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michal Jaegermann <michal> | ||||
| Component: | gdb | Assignee: | Jan Kratochvil <jan.kratochvil> | ||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | rawhide | CC: | dvlasenk, jan.kratochvil | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2009-02-09 12:36:10 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Michal Jaegermann
2009-01-13 01:18:44 UTC
No, this looks as an original bug report. It comes from an inlining support which is not being imported upstream and being maintained separately, from: http://sourceware.org/ml/gdb-patches/2008-07/msg00442.html Shortly tried to reproduce it with no luck. Do you have some testcase you could provide, please? > Do you have some testcase you could provide, please? I wish. gdb dumped that on me while I was trying to do some walk through /usr/sbin/privoxy; mostly to confirm that bug 479781 no longer applies and because I already had 'privoxy-debuginfo' on hands because of other, earlier, issues. While stepping deeper in an inner "wait" loop, I guess in some static inlined function, I typed "fin" and got a notification from gdb that an "internal problem occured" and I may want to see a core. I am not sure how to reproduce that but I have that core around if of any interest. I may try more times if there is some (semi?) reliable way to reproduce but originally I did not get very far. I think that I may have a repeatable test case. In a directory with a copy of /usr/sbin/privoxy from privoxy-3.0.10-2.fc11.x86_64 and with privoxy-debuginfo-3.0.10-2.fc11 (actually after 'debuginfo-install privoxy' which installs other packages too) and with the following .gdbinit file: dir /usr/src/debug/privoxy-3.0.10-stable/ set args --no-daemon /etc/privoxy/config b main b jcc.c:3457 b jcc.c:3434 After 'debuginfo-install gdb' and from emacs "gud" interface I see the following: .... (gdb) c Continuing. Jan 13 17:43:19.546 Privoxy(7ffff7fdf6f0) Info: Privoxy version 3.0.10 Jan 13 17:43:19.546 Privoxy(7ffff7fdf6f0) Info: Program name: /var/tmp/privoxy/privoxy Breakpoint 2, bind_port_helper (config=0x63cc10) at jcc.c:3457 (gdb) fin Run till exit from #0 bind_port_helper (config=0x63cc10) at jcc.c:3457 ../../gdb/breakpoint.c:4917: internal-error: set_momentary_breakpoint: Assertion `!frame_id_inlined_p (frame_id)' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) So far I repeated that three times and it looks like that "fin" from the second breakpoint does the job. I am not sure if this detail that already another instance of privoxy, started from a boot sequence, is running is significant or not. |