Bug#340659: sed bug #340659; segmentation fault

2005-12-10 Thread Justin Pryzby
On Sat, Dec 10, 2005 at 11:08:03AM +0100, Jakub Wilk wrote:
 Could you please confirm that Debian bug #340659: sed: 
 s/(.{3})/\1/ -- segmentation fault is fixed, at least in sed 
 4.1.4-4 from unstable?
 No, sed 4.1.4-4 still segfaults.
Thats strage; it works here.  Could run it under valgrind or gdb?

$ valgrind sed ...

gdb --args sed ...
(gdb) r
...
(gdb) bt

-- 
Clear skies,
Justin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#340659: sed bug #340659; segmentation fault

2005-12-10 Thread Clint Adams
This may have been closed incorrectly.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#340659: sed bug #340659; segmentation fault

2005-12-10 Thread Jakub Wilk
Could you please confirm that Debian bug #340659: sed: 
s/(.{3})/\1/ -- segmentation fault is fixed, at least in sed 
4.1.4-4 from unstable?

No, sed 4.1.4-4 still segfaults.

Thats strage; it works here.  Could run it under valgrind or gdb?

Sure, here's the valgrind's output (sed 4.1.4-4):

#v+
Conditional jump or move depends on uninitialised value(s)
  at 0x1B8ECB13: (within /lib/ld-2.3.5.so)
  by 0x1B8E631C: (within /lib/ld-2.3.5.so)
  by 0x1B8F2BDD: (within /lib/ld-2.3.5.so)
  by 0x1B8E7675: (within /lib/ld-2.3.5.so)
  by 0x1B8E47C6: (within /lib/ld-2.3.5.so)

Conditional jump or move depends on uninitialised value(s)
  at 0x1B8EC7D3: (within /lib/ld-2.3.5.so)
  by 0x1B8E631C: (within /lib/ld-2.3.5.so)
  by 0x1B8F2BDD: (within /lib/ld-2.3.5.so)
  by 0x1B8E7675: (within /lib/ld-2.3.5.so)
  by 0x1B8E47C6: (within /lib/ld-2.3.5.so)

Conditional jump or move depends on uninitialised value(s)
  at 0x1B8EC6B6: (within /lib/ld-2.3.5.so)
  by 0x1B8E6376: (within /lib/ld-2.3.5.so)
  by 0x1B8F2BDD: (within /lib/ld-2.3.5.so)
  by 0x1B8E7675: (within /lib/ld-2.3.5.so)
  by 0x1B8E47C6: (within /lib/ld-2.3.5.so)

Conditional jump or move depends on uninitialised value(s)
  at 0x1B8EC6C2: (within /lib/ld-2.3.5.so)
  by 0x1B8E6376: (within /lib/ld-2.3.5.so)
  by 0x1B8F2BDD: (within /lib/ld-2.3.5.so)
  by 0x1B8E7675: (within /lib/ld-2.3.5.so)
  by 0x1B8E47C6: (within /lib/ld-2.3.5.so)

Conditional jump or move depends on uninitialised value(s)
  at 0x1B8EC7D3: (within /lib/ld-2.3.5.so)
  by 0x1B8E6376: (within /lib/ld-2.3.5.so)
  by 0x1B8F2BDD: (within /lib/ld-2.3.5.so)
  by 0x1B8E7675: (within /lib/ld-2.3.5.so)
  by 0x1B8E47C6: (within /lib/ld-2.3.5.so)

Invalid read of size 4
  at 0x1B9B437B: (within /lib/tls/libc-2.3.5.so)
  by 0x1B9BF87C: (within /lib/tls/libc-2.3.5.so)
  by 0x1B9BFCFE: re_compile_pattern (in /lib/tls/libc-2.3.5.so)
  by 0x804E2C5: (within /bin/sed)
  by 0x804E3B5: (within /bin/sed)
  by 0x804B539: (within /bin/sed)
  by 0x804BB76: (within /bin/sed)
  by 0x804977D: (within /bin/sed)
  by 0x1B926ECF: __libc_start_main (in /lib/tls/libc-2.3.5.so)
  by 0x80493A0: (within /bin/sed)
Address 0x1BFF5F60 is not stack'd, malloc'd or (recently) free'd

Process terminating with default action of signal 11 (SIGSEGV)
Access not within mapped region at address 0x1BFF5F60
  at 0x1B9B437B: (within /lib/tls/libc-2.3.5.so)
  by 0x1B9BF87C: (within /lib/tls/libc-2.3.5.so)
  by 0x1B9BFCFE: re_compile_pattern (in /lib/tls/libc-2.3.5.so)
  by 0x804E2C5: (within /bin/sed)
  by 0x804E3B5: (within /bin/sed)
  by 0x804B539: (within /bin/sed)
  by 0x804BB76: (within /bin/sed)
  by 0x804977D: (within /bin/sed)
  by 0x1B926ECF: __libc_start_main (in /lib/tls/libc-2.3.5.so)
  by 0x80493A0: (within /bin/sed)

ERROR SUMMARY: 14 errors from 6 contexts (suppressed: 0 from 0)
malloc/free: in use at exit: 4759281 bytes in 2420 blocks.
malloc/free: 2452 allocs, 32 frees, 5121680 bytes allocated.
For counts of detected errors, rerun with: -v
searching for pointers to 2420 not-freed blocks.
checked 4841196 bytes.

LEAK SUMMARY:
  definitely lost: 0 bytes in 0 blocks.
possibly lost: 0 bytes in 0 blocks.
  still reachable: 4759281 bytes in 2420 blocks.
   suppressed: 0 bytes in 0 blocks.
Reachable blocks (those to which a pointer was found) are not shown.
To see them, rerun with: --show-reachable=yes
#v-

--
Jakub Wilk


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#340659: sed bug #340659; segmentation fault

2005-12-10 Thread Justin Pryzby
On Sat, Dec 10, 2005 at 05:11:09PM +0100, Jakub Wilk wrote:
 Could you please confirm that Debian bug #340659: sed: 
 s/(.{3})/\1/ -- segmentation fault is fixed, at least in sed 
 4.1.4-4 from unstable?
 No, sed 4.1.4-4 still segfaults.
 Thats strage; it works here.  Could run it under valgrind or gdb?
 Sure, here's the valgrind's output (sed 4.1.4-4):
 
 #v+
 Conditional jump or move depends on uninitialised value(s)
   at 0x1B8ECB13: (within /lib/ld-2.3.5.so)
These are expected with libc235.

 Invalid read of size 4
   at 0x1B9B437B: (within /lib/tls/libc-2.3.5.so)
   by 0x1B9BF87C: (within /lib/tls/libc-2.3.5.so)
   by 0x1B9BFCFE: re_compile_pattern (in /lib/tls/libc-2.3.5.so)
   by 0x804E2C5: (within /bin/sed)
   by 0x804E3B5: (within /bin/sed)
   by 0x804B539: (within /bin/sed)
   by 0x804BB76: (within /bin/sed)
   by 0x804977D: (within /bin/sed)
   by 0x1B926ECF: __libc_start_main (in /lib/tls/libc-2.3.5.so)
   by 0x80493A0: (within /bin/sed)
 Address 0x1BFF5F60 is not stack'd, malloc'd or (recently) free'd
This is at least marginally useful.  Would you consider compiling sed
locally with export DEB_BUILD_OPTIONS=nostrip set?  That will allow a
better backtrace.

Also, Clint just uploaded 4.1.4-5, which closes this bug.  I don't
know what he meant, This may have been closed incorrectly.; I might
have caused some confusion by digging into the bugs while he was
preparing an upload.  Anyway, could you test the new version?  It is
not yet installed into the archive, so you'll have to use
http://incoming.debian.org/.  Actually, 386 packages aren't even
available yet.  You could wait a short while until they show up, or
build yourself from the .diff at incoming.d.o and the .orig at
ftp.d.o, or I could build it for you.

-- 
Clear skies,
Justin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#340659: sed bug #340659; segmentation fault

2005-12-10 Thread Jakub Wilk

* Justin Pryzby [EMAIL PROTECTED], 2005-12-10, 11:30:
Also, Clint just uploaded 4.1.4-5, which closes this bug. I don't know 
what he meant, This may have been closed incorrectly.; I might

have caused some confusion by digging into the bugs while he was
preparing an upload. Anyway, could you test the new version?

The new version is still crashing.
But now I can see this is not a sed's bug.
The following program segfaults, too:

#include regex.h

int main(void)
{
 static struct re_pattern_buffer b;
 re_set_syntax(RE_SYNTAX_POSIX_EXTENDED);
 re_compile_pattern((.{3}), 10, b);
 return 0;
}

--
Jakub Wilk


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#340659: sed bug #340659; segmentation fault

2005-12-10 Thread Clint Adams
reopen 340659
reassign 340659 libc6
retitle 340659 segfault when re_compiling (.{3})
thanks

 The new version is still crashing.
 But now I can see this is not a sed's bug.
 The following program segfaults, too:
 
 #include regex.h
 
 int main(void)
 {
  static struct re_pattern_buffer b;
  re_set_syntax(RE_SYNTAX_POSIX_EXTENDED);
  re_compile_pattern((.{3}), 10, b);
  return 0;
 }


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]