Bug 118593 - gdb always stops in _dl_catch_error if doing single stepping
Summary: gdb always stops in _dl_catch_error if doing single stepping
Status: RESOLVED WORKSFORME
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Development (show other bugs)
Version: RC 4
Hardware: 32bit All
: P5 - None : Normal
Target Milestone: ---
Assignee: Andreas Schwab
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-23 15:42 UTC by Karsten Keil
Modified: 2005-11-11 18:11 UTC (History)
0 users

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
bzip2 tar archive for xisdnload testcase (43.59 KB, application/octet-stream)
2005-11-07 22:41 UTC, Karsten Keil
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Karsten Keil 2005-09-23 15:42:11 UTC
While debugging a X11 program I want to do single stepping on the top level 
of the program. But if it is loading libs via dlopen, it always stops on 
_dl_catch_error. I did not enable anz special catch points.
Comment 1 Andreas Schwab 2005-10-21 14:41:13 UTC
Single stepping always steps until a different source line is reached.
Comment 2 Karsten Keil 2005-10-24 16:39:15 UTC
But next should stop on the next program line in the same source and should not doing signle stepping into the function call.
Comment 3 Andreas Schwab 2005-11-07 15:22:05 UTC
Please provide a fully-contained test case.
Comment 4 Karsten Keil 2005-11-07 22:41:11 UTC
Created attachment 56641 [details]
bzip2 tar archive for xisdnload testcase

you do not need any isdn equipment for this testcase, but you need to load the module isdn (modprobe isdn).
Then do following to see the issue:
cd isdn4k-utils/xisdnload
gdb ./xisdnload
break 519
run
n
n
and you are not on the next line, but in _dl_catch_error()
Comment 5 Andreas Schwab 2005-11-11 13:53:24 UTC
Works fine here.
Comment 6 Karsten Keil 2005-11-11 18:11:22 UTC
Which version ?
Any special gdb setttings ?
I'm using 10.0 final and no extra gdb init file.