#643: 1.3.0 crash after 1.2.7 even once was run in 1.3.0's workdir
----------------------+-----------------------------------------------------
Reporter: nobody | Owner:
Type: defect | Status: closed
Priority: normal | Milestone:
Component: system | Version: 1.3.0
Resolution: invalid | Keywords:
----------------------+-----------------------------------------------------
Changes (by erijo):
* status: new => closed
* resolution: None => invalid
Old description:
> 1.2.7 running in 1.3.0's working directory, changes users.conf file
> removing ".Licq"
> at the each ends of lines. 1.3.0 crashes in that working directory (a-la:
> .licq) after that:
>
> Licq Segmentation Violation Detected.
> Backtrace:
> [0x80dc2ae]
> /lib/tls/libc.so.6 [0x77af38]
> [0x80b9348]
> [(nil)]
> Attempting to generate core file.
> Aborted
>
> gdb points to strncpy() function. So, there is an error in parse function
> in 1.3.0 version.
New description:
1.2.7 running in 1.3.0's working directory, changes users.conf file
removing ".Licq" at the each ends of lines. 1.3.0 crashes in that working
directory (a-la: .licq) after that:
{{{
Licq Segmentation Violation Detected.
Backtrace:
[0x80dc2ae]
/lib/tls/libc.so.6 [0x77af38]
[0x80b9348]
[(nil)]
Attempting to generate core file.
Aborted
}}}
gdb points to strncpy() function. So, there is an error in parse function
in 1.3.0 version.
Comment:
Licq don't support "downgrading" the basedir.
--
Ticket URL: <http://trac.licq.org/ticket/643#comment:1>
Licq <http://trac.licq.org/>
Licq - an instant messaging client for UNIX.