|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Novell Archives Archived content from Novell openSUSE support forums |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
On SuSE 9.3 glibc 2.3.4 is compiled in such a way that the "write()" function
gets inlined in the _IO_new_file_write routine. This makes it impossible to properly intercept all calls to write() for a project I am working on. I checked an older SuSE (8.0) and also RHEL 4.0 and neither seem to have this problem. Where is the proper place to report a bug like this... Thanks, Vince |
|
|||
|
vince@deater.net wrote:
> On SuSE 9.3 glibc 2.3.4 is compiled in such a way that the "write()" function > gets inlined in the _IO_new_file_write routine. > > This makes it impossible to properly intercept all calls to write() for a > project I am working on. > > I checked an older SuSE (8.0) and also RHEL 4.0 and neither seem to have > this problem. > > Where is the proper place to report a bug like this... The Suse bug registration system. I don't know the URL, but I think "feedback" is part of it. If you are feeling ambitious, you could also figure out if glibc 2.3.4 has the same problem in its original version (the tarball before Suse possibly patched it and made the RPM). If there is a real bug in glibc, it would be good to bring it to the attention of the authors ASAP. Check the GNU site. Mark |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|