Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6332113
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 24, 20262026-05-24T18:12:01+00:00 2026-05-24T18:12:01+00:00

I am working with a legacy code ported from Visual C++ 6.0 to VC++

  • 0

I am working with a legacy code ported from Visual C++ 6.0 to VC++ 9.0 (2008). I disabled the secure CRT warnings using _CRT_SECURE_NO_WARNINGS pre-processor definition. But that has lead to crashes in the std::vector destructor.

Any issues in using _CRT_SECURE_NO_WARNINGS?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-24T18:12:02+00:00Added an answer on May 24, 2026 at 6:12 pm

    How is it crashing? This sounds more like you’ve got memory in one location overwriting memory in your vector, then freeing it before your vector is freed. I’d look to any place with pointers. Since you’re now on a standards compliant compiler replace them with boost shared pointers or boost arrays. Anything to remove the need for pointer arithmetic where an iterator would be safer to use.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm working on getting some legacy code under test, and we're using Moq 4
I'm looking into using a IOC container but I'm working with legacy code and
I am working with some legacy code where I am using a column value
We are working with some legacy code that accesses a shared drive by the
I'm working with legacy Java code which returns java.lang.object. I'm passing it into a
I am working with some legacy code, and at some point there is a
I am working on a legacy code where an application uses AxSHDocVw.AxWebBrowser ( not
I just recently finished Michael Feathers' book Working Effectively with Legacy Code . It
I have been working on some legacy C++ code that uses variable length structures
I have some really complicated legacy code I've been working on that crashes when

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.