Red Hat Bugzilla – Bug 479781
gdb trips on "finish" command
Last modified: 2009-02-09 07:36:10 EST
Created attachment 328811 [details]
backtrace from gdb
Description of problem:
gdb got confused in a debuggin session and after "finish" command informed me that further debugging will be "unreliable". It offered to dump a core from an incident and a backtrace from it is attached.
It this is the same issue as bug 479381? That was not clear to me
Version-Release number of selected component (if applicable):
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:
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:
set args --no-daemon /etc/privoxy/config
After 'debuginfo-install gdb' and from emacs "gud" interface I see the following:
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
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.
* Mon Feb 9 2009 Jan Kratochvil <firstname.lastname@example.org> - 126.96.36.19981214-2
- Fix crash / implement `finish' into inlined functions (BZ 479781).